This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 1/4] 'catch syscall' feature -- Architecture-independent part


On Wed, Nov 05, 2008 at 12:21:05AM +0200, Eli Zaretskii wrote:
> > ... but from what you are saying it seems that in Windows it's
> > different. What's the proper datatype to represent a syscall there?
> 
> A symbol, I think.

As far as I can tell, Windows has system calls just like other OS's
do; as of Windows NT they were triggered by "int 2e" and the syscall
number went in %eax.

There's plenty of other levels of potential traceability in a Windows
program than the system call, but I think that's the obvious one to
map "catch syscall" on to.  Although, I don't believe GDB will be able
to catch Windows syscalls; I don't see a way to do it, anyway, but
there's plenty I don't know about Windows.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]