From: Gary Benson <gbenson@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH] Prompt user to report bugs
Date: Wed, 14 May 2014 13:15:00 -0000 [thread overview]
Message-ID: <20140514131511.GA26388@blade.nx> (raw)
In-Reply-To: <5373634B.2000007@codesourcery.com>
Yao Qi wrote:
> On 05/14/2014 07:07 PM, Gary Benson wrote:
> > This patch prints a couple of extra lines in internal_vproblem
> > to prompt the user to report the bug that's just happened.
>
> GDB prints that when it starts.
>
> $ ./gdb
> GNU gdb (GDB) 7.7.50.20140514-cvs
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Do we want to print the same message again in internal error
> message?
Yes, I think so. The internal error could occur many thousands
of lines after the startup message is printed.
Thanks,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2014-05-14 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 11:07 Gary Benson
2014-05-14 11:22 ` Mark Kettenis
2014-05-14 12:39 ` Yao Qi
2014-05-14 13:15 ` Gary Benson [this message]
2014-05-14 20:14 ` Tom Tromey
2014-05-14 21:05 ` Doug Evans
2014-05-14 21:11 ` Paul_Koning
2014-05-14 22:24 ` Doug Evans
2014-05-15 11:39 ` Gary Benson
2014-05-15 17:10 ` Doug Evans
2014-05-15 10:07 ` Pierre Muller
2014-05-15 11:38 ` Gary Benson
2014-05-27 14:43 ` [COMMITTED PATCH] " Gary Benson
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=20140514131511.GA26388@blade.nx \
--to=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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