Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Sérgio Durigan Júnior'" <sergiodj@linux.vnet.ibm.com>,
	gdb-patches@sourceware.org
Subject: RE: [PATCH 0/4] 'catch syscall' feature -- Introduction
Date: Tue, 04 Nov 2008 08:28:00 -0000	[thread overview]
Message-ID: <000001c93e57$20856620$61903260$@u-strasbg.fr> (raw)
In-Reply-To: <1225773077.24532.51.camel@miki>

  I had just one question about this:

  This patch is linux specific in its current state,
but I thought (but you are welcome to correct me if I am wrong,
as I am unsure of what follows) that other operating systems
also use syscalls (like FreeBSD or NetBSD, probably others also).

  If my previous statement is wrong, you can skip
what is following, otherwise my questions are:
1) Do all OS using syscalls use the same number to
functionality correspondence?
2) Do all OS follow the "linux" habit of never changing the
syscall numbers in changing versions?

If the answer to 2) is NO, it probably means that
extending this patch to such OS's will be harder...

Even if we stick to linux only for now,
shouldn't we explicitly add linux in the name of the processor-dependent
xml files?

This would make it easier to extend the feature to other OS's
later, no?


Pierre Muller
Pascal language support maintainer for GDB



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Sérgio Durigan Júnior
> Envoyé : Tuesday, November 04, 2008 5:31 AM
> À : gdb-patches@sourceware.org
> Objet : [PATCH 0/4] 'catch syscall' feature -- Introduction
> 
> Hello guys,
> 
> This is the new version of the "catch syscall" patch. I have reviewed
> it
> for a while, fixing things that you have proposed to me and
> implementing
> new code. Basically, the changes are:
> 
> - Grammar errors fixed (including the "two-spaces-after-dot" rule) (as
> pointed out by Michael).
> 
> - Rework of the "arch independent" part of the patch, now using the new
> breakpoint_ops mechanism (as implemented by Joel).
> 
> - Tab-completion support (as suggested by Tromey).
> 
> - Storing the syscalls names using XML support, and not directly in the
> source-code (as requested by Daniel Jacobowits).
> 
> - PPC, PPC64 and i386 support.
> 
> - Implementation of the GDB's datadir (Daniel asked this too).
> 
> Well, I think that's it. You guys already know what this patch is
> supposed to do, but in case you have forgotten:
> 
> http://sourceware.org/ml/gdb-patches/2008-09/msg00583.html
> 
> Hope you like it :-).
> 
> Best regards,
> 
> --
> Sérgio Durigan Júnior
> Linux on Power Toolchain - Software Engineer
> Linux Technology Center - LTC
> IBM Brazil


  reply	other threads:[~2008-11-04  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04  4:32 Sérgio Durigan Júnior
2008-11-04  8:28 ` Pierre Muller [this message]
2008-11-04 13:48   ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001c93e57$20856620$61903260$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox