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

> Date: Tue, 4 Nov 2008 17:34:21 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
> 	sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org
> 
> 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.

This level is IMO uninteresting, because many important system
services on Windows are not in the kernel space.

I'd like us very much to have some higher-level abstraction of a
syscall in target-independent code, than just a number.  Can we do
that, please?
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]