From: Eli Zaretskii <eliz@gnu.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] catch syscall -- try 5 -- Build-system, testcase, documentation and extra command
Date: Sun, 26 Apr 2009 18:52:00 -0000 [thread overview]
Message-ID: <831vrffdt2.fsf@gnu.org> (raw)
In-Reply-To: <1240769095.13755.24.camel@miki>
> From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= <sergiodj@linux.vnet.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Sun, 26 Apr 2009 15:04:54 -0300
>
> > @var{name} can be any system call name that is valid for the
> > underlying OS. Just what syscalls are valid depends on the OS. On
> > GNU and Unix systems, you can find the full list of valid syscall
> > names on <PUT HERE THE NAME OF SYSTEM FILE WHERE TO FIND THE LIST>.
>
> I'm having a hard time trying to figure out what to put in "<PUT HERE
> THE NAME OF SYSTEM FILE WHERE TO FIND THE LIST>".
How about the header file from the kernel sources which you mentioned
in the XML files? Like this one, from x86 Linux:
/usr/src/linux/arch/x86/include/asm/unistd_32.h
Unless there's a better place to point the readers, that is. Maybe
some URL?
If there's no good place to look for that on your garden-variety
system, just delete that sentence.
next prev parent reply other threads:[~2009-04-26 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 0:34 Sérgio Durigan Júnior
2009-04-25 8:44 ` Eli Zaretskii
2009-04-26 7:32 ` Sérgio Durigan Júnior
2009-04-26 17:48 ` Eli Zaretskii
2009-04-26 17:55 ` Sérgio Durigan Júnior
2009-04-26 18:05 ` Sérgio Durigan Júnior
2009-04-26 18:52 ` Eli Zaretskii [this message]
2009-04-26 21:29 ` Sérgio Durigan Júnior
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=831vrffdt2.fsf@gnu.org \
--to=eliz@gnu.org \
--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