From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: palves@redhat.com, gdb@sourceware.org
Subject: Re: Time to expand "Program received signal" ?
Date: Tue, 13 Nov 2012 17:23:00 -0000 [thread overview]
Message-ID: <20121113172237.GY4847@adacore.com> (raw)
In-Reply-To: <201211131640.qADGeKhs021376@glazunov.sibelius.xs4all.nl>
> I do find the strings somewhat long though. The lines wrap, and that
> distracts people from the important bit, which is that a signal was
> received. Are people really interested in the bit between. Isn't it
> better to print just:
>
> Thread 2 received signal SIGUSR1, User defined signal 1.
>
> Folks can then use "info threads" to look at the details of the thread.
Same here, and I'd be OK with the output you suggest. But the extra
info might be useful if the thread disappeared before the user had
a chance to do "info threads"... Perhaps this is a good situation
where we should provide an option, so that the short output is used
by default, but still allow a longer output when needed.
--
Joel
prev parent reply other threads:[~2012-11-13 17:23 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
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 ` 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 18:27 ` Paul_Koning
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 [this message]
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=20121113172237.GY4847@adacore.com \
--to=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