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 4/4] 'catch syscall' feature -- Build system, documentation and testcase
Date: Tue, 04 Nov 2008 20:54:00 -0000 [thread overview]
Message-ID: <ud4hbusaa.fsf@gnu.org> (raw)
In-Reply-To: <1225773088.24532.56.camel@miki>
> From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= <sergiodj@linux.vnet.ibm.com>
> Date: Tue, 04 Nov 2008 02:31:28 -0200
>
> This last part modifies the build system (in order to implement the
> GDB's datadir), adds the documentation and the testcase for the new
> feature.
Thanks.
However,
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 261d1c7..3641fff 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -3635,6 +3635,12 @@ A failed Ada assertion.
> A call to @code{exec}. This is currently only available for HP-UX
> and @sc{gnu}/Linux.
>
> +@item syscall
> +@itemx syscall @var{syscall name}
> +@cindex break on call to/return from a system call
> +A call to/return from a @code{syscall} -- similar to the @code{strace}
> +utility.
...this is not really a user documentation. Please describe the
feature instead of sending the reader to look for external
documentation of an unrelated utility, which, btw, is available only
on some versions of Unix, but not on others.
At the very least, we should explain what is @var{syscall name}. An
example of usage and typical GDB output get bonus points.
Thanks.
next prev parent reply other threads:[~2008-11-04 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 4:32 Sérgio Durigan Júnior
2008-11-04 8:19 ` Phil Muldoon
2008-11-04 15:03 ` Sérgio Durigan Júnior
2008-11-04 15:16 ` Daniel Jacobowitz
2008-11-04 15:36 ` Sérgio Durigan Júnior
2008-11-04 15:50 ` Daniel Jacobowitz
2008-11-04 16:33 ` Tom Tromey
2008-11-07 4:03 ` Sérgio Durigan Júnior
2008-11-04 20:03 ` Pedro Alves
2008-11-04 20:33 ` Sérgio Durigan Júnior
2008-11-04 20:47 ` Pedro Alves
2008-11-04 20:54 ` Eli Zaretskii [this message]
2008-11-07 3:58 ` 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=ud4hbusaa.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