This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/3] catch syscall -- try 5 -- Build-system, testcase, documentation and extra command
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Sérgio Durigan Júnior <sergiodj at linux dot vnet dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 26 Apr 2009 21:52:09 +0300
- Subject: Re: [PATCH 3/3] catch syscall -- try 5 -- Build-system, testcase, documentation and extra command
- References: <1240446783.2000.83.camel@miki> <83prf1f7hb.fsf@gnu.org> <1240769095.13755.24.camel@miki>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.