From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] gdbserver 2/n - signals
Date: Fri, 20 Jul 2001 08:33:00 -0000 [thread overview]
Message-ID: <20010720083249.A21309@nevyn.them.org> (raw)
In-Reply-To: <9003-Fri20Jul2001103107+0300-eliz@is.elta.co.il>
On Fri, Jul 20, 2001 at 10:31:08AM +0300, Eli Zaretskii wrote:
> > Date: Thu, 19 Jul 2001 14:52:37 -0700
> > From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
> >
> > 2001-07-19 Daniel Jacobowitz <drow@mvista.com>
> >
> > * gdb.texinfo (Protocol): Mention that signal numbers
> > are defined by the target_signal enum.
> >
> > Index: gdb.texinfo
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> > retrieving revision 1.44
> > diff -u -r1.44 gdb.texinfo
> > --- gdb.texinfo 2001/07/06 04:07:29 1.44
> > +++ gdb.texinfo 2001/07/19 18:56:55
> > @@ -10211,8 +10211,8 @@
> > receive any of the below as a reply. In the case of the @samp{C},
> > @samp{c}, @samp{S} and @samp{s} packets, that reply is only returned
> > when the target halts. In the below the exact meaning of @samp{signal
> > -number} is poorly defined. In general one of the UNIX signal numbering
> > -conventions is used.
> > +number} is defined by the type @code{enum target_signal}. For the most
> > +common signals this corresponds to the UNIX signal numbering conventions.
>
> I don't really understand the rationale for this change. This is a
> user's manual; why should it matter to a user to know the name of the
> enum which defines signal numbers? I don't see how it makes the issue
> better defined (since you removed the ``poorly defined'' phrase).
>
> If we do want to leave the `enum target_signal' info in the manual, at
> the very least please say what source file is that defined on.
Well, the way I see it is that the signal numbering convention is part
of the remote protocol, and so should be documented in the manual; at
the same time I didn't really want to duplicate the hundred and
something signals inline in the texinfo documentation.
I don't really understand why the remote protocol is documented in the
user's manual, either :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-20 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 12:01 Daniel Jacobowitz
2001-07-19 14:00 ` Andrew Cagney
2001-07-19 14:17 ` Daniel Jacobowitz
2001-07-19 14:49 ` Andrew Cagney
2001-07-19 14:52 ` Daniel Jacobowitz
2001-07-19 15:21 ` Andrew Cagney
2001-07-20 0:32 ` Eli Zaretskii
2001-07-20 8:33 ` Daniel Jacobowitz [this message]
2001-07-20 11:31 ` Eli Zaretskii
2001-07-20 11:34 ` Daniel Jacobowitz
2001-07-21 0:38 ` Eli Zaretskii
2001-07-20 16:48 ` Andrew Cagney
2001-07-21 1:04 ` Eli Zaretskii
2001-07-20 16:42 ` Andrew Cagney
2001-07-19 17:22 ` Kevin Buettner
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=20010720083249.A21309@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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