From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-59680-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 5099 invoked by alias); 5 Nov 2008 04:19:02 -0000
Received: (qmail 5052 invoked by uid 22791); 5 Nov 2008 04:19:02 -0000
X-Spam-Check-By: sourceware.org
Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Nov 2008 04:18:20 +0000
Received: from HOME-C4E4A596F7 ([77.126.241.172]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K9U00000EPC1UK1@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Wed, 05 Nov 2008 06:20:01 +0200 (IST)
Date: Wed, 05 Nov 2008 04:19:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH 1/4] 'catch syscall' feature -- Architecture-independent	part
In-reply-to: <20081104223421.GC5391@caradoc.them.org>
X-012-Sender: halo1@inter.net.il
To: Daniel Jacobowitz <drow@false.org>
Cc: bauerman@br.ibm.com, sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <ur65qu7ov.fsf@gnu.org>
References: <1225773079.24532.52.camel@miki> <ubpwvureh.fsf@gnu.org> <1225836687.20764.21.camel@localhost.localdomain> <uvdv3t9ny.fsf@gnu.org> <20081104223421.GC5391@caradoc.them.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-11/txt/msg00071.txt.bz2

> 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?