From: John Gilmore <gnu@toad.com>
To: Pedro Alves <palves@redhat.com>
Cc: John Gilmore <gnu@toad.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
brobecker@adacore.com, gdb@sourceware.org
Subject: Re: Time to expand "Program received signal" ?
Date: Wed, 14 Nov 2012 19:54:00 -0000 [thread overview]
Message-ID: <201211141954.qAEJsQ2N026469@new.toad.com> (raw)
In-Reply-To: <50A371C6.3080307@redhat.com>
> > GDB shouldn't mention threads at all, unless the program being debugged
> > is multi-threaded.
>
> Since 7.0 GDB models non-threaded programs as single threaded.
OK, then, you can call it what you want. GDB shouldn't mention
threads at all, unless the program being debugged has more than a
single thread.
Printing a thread identifier is extraneous information that the user
will just have to skip over to get to the real information (that their
program got a signal).
John
next prev parent reply other threads:[~2012-11-14 19:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:27 Pedro Alves
2012-11-13 16:25 ` Joel Brobecker
2012-11-13 16:40 ` Mark Kettenis
2012-11-13 17:22 ` Pedro Alves
2012-11-13 22:40 ` John Gilmore
2012-11-14 10:26 ` Pedro Alves
2012-11-14 19:54 ` John Gilmore [this message]
2012-11-15 10:36 ` Pedro Alves
2012-11-15 16:58 ` Eli Zaretskii
2012-11-15 17:21 ` Pedro Alves
2012-11-15 17:51 ` Joel Brobecker
2012-11-15 18:16 ` Eli Zaretskii
2012-11-15 18:27 ` Paul_Koning
2012-11-15 18:27 ` Pedro Alves
2012-11-15 19:07 ` Eli Zaretskii
2012-11-15 20:33 ` Pedro Alves
2012-11-15 20:58 ` Eli Zaretskii
2012-11-15 19:27 ` Tom Tromey
2012-11-15 22:21 ` John Gilmore
2012-11-15 22:27 ` Paul_Koning
2012-11-16 0:22 ` John Gilmore
2012-11-16 8:25 ` Eli Zaretskii
2012-11-13 17:23 ` Joel Brobecker
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=201211141954.qAEJsQ2N026469@new.toad.com \
--to=gnu@toad.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@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