Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] 'catch syscall' feature -- XML support part
Date: Tue, 04 Nov 2008 15:13:00 -0000	[thread overview]
Message-ID: <20081104151229.GA32619@caradoc.them.org> (raw)
In-Reply-To: <1225811056.32321.9.camel@miki>

On Tue, Nov 04, 2008 at 01:04:16PM -0200, Sérgio Durigan Júnior wrote:
> Hi Daniel,
> 
> On Tue, 2008-11-04 at 08:47 -0500, Daniel Jacobowitz wrote:
> > On Tue, Nov 04, 2008 at 02:35:55PM +0100, Mark Kettenis wrote:
> > > Hmm, I haven't looked at the code yes, but this is all Linux-specific
> > > stuff, so this should be reflected in the names of those files.
> > 
> > Yes please.  We should be able to do non-Linux syscalls too, but
> > they'll require different data files.
> > 
> > Sergio, while you're moving them, could they go in a subdirectory
> > please?  Maybe gdb/syscalls/ ?  It doesn't need to have a separate
> > ChangeLog or Makefile or anything like that.
> 
> IIUC, you're asking me to put the XML files in gdb/syscalls/ right?
> Well, they are already there :-). I think the correct approach to solve
> this problem is renaming the XML files to something like
> "i386-linux-syscalls.xml", isn't it?

Oh whoops - then since the ChangeLog is in gdb/ChangeLog, the entry
should refer to "syscalls/i386-syscalls.xml" instead of just
"i386-syscalls.xml".  How about renaming to "syscalls/i386-linux.xml"?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-11-04 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04  4:32 Sérgio Durigan Júnior
2008-11-04 13:36 ` Mark Kettenis
2008-11-04 13:47   ` Daniel Jacobowitz
2008-11-04 15:05     ` Sérgio Durigan Júnior
2008-11-04 15:13       ` Daniel Jacobowitz [this message]
2008-11-04 15:18         ` Sérgio Durigan Júnior
2008-11-04 15:06   ` Sérgio Durigan Júnior
2008-11-08 19:06     ` Mark Kettenis
2008-11-04 18:41 ` Tom Tromey
2008-11-07  3:46   ` Sérgio Durigan Júnior
2008-11-07 18:24     ` Tom Tromey
2008-11-04 21:20 ` Eli Zaretskii
2008-11-04 22:23   ` Daniel Jacobowitz
2008-11-04 22:27     ` Eli Zaretskii
2008-11-04 22:36       ` Daniel Jacobowitz
2008-11-05  1:02         ` Sérgio Durigan Júnior
2008-11-05  4:22         ` Eli Zaretskii
2008-11-05 14:57           ` 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=20081104151229.GA32619@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --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