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: Sérgio Durigan Júnior <sergiodj at linux dot vnet dot ibm dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 26 Apr 2009 15:04:54 -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>
Hi Eli,
Just one question that I forgot to ask.
On Sat, 2009-04-25 at 11:44 +0300, Eli Zaretskii wrote:
> @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>". Basically, I'd like
to write something like "... valid syscall names on the XML files inside
@file{syscalls/} directory.", but I should mention where the syscalls/
directory is located, right? Do you have any ideas on how to write
this?
Thanks,
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil