From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gbenson@redhat.com
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [PATCH] Prompt user to report bugs
Date: Wed, 14 May 2014 11:22:00 -0000 [thread overview]
Message-ID: <201405141122.s4EBME4c030348@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20140514110742.GA25550@blade.nx> (message from Gary Benson on Wed, 14 May 2014 12:07:42 +0100)
> Date: Wed, 14 May 2014 12:07:42 +0100
> From: Gary Benson <gbenson@redhat.com>
>
> Hi all,
>
> This patch prints a couple of extra lines in internal_vproblem
> to prompt the user to report the bug that's just happened.
>
> Ok to commit?
Can't hurt.
> --
> 2014-05-14 Gary Benson <gbenson@redhat.com>
>
> * utils.c (internal_vproblem): Prompt the user to file a report.
>
> diff --git a/gdb/utils.c b/gdb/utils.c
> index a8a7cb3..905ce6d 100644
> --- a/gdb/utils.c
> +++ b/gdb/utils.c
> @@ -746,6 +746,14 @@ internal_vproblem (struct internal_problem *problem,
> else
> internal_error (__FILE__, __LINE__, _("bad switch"));
>
> + fputs_unfiltered (_("\nThis is a bug, please report it."), gdb_stderr);
> + if (REPORT_BUGS_TO[0])
> + {
> + fputs_unfiltered (_(" For instructions, see:\n"), gdb_stderr);
> + fprintf_unfiltered (gdb_stderr, _("%s."), REPORT_BUGS_TO);
> + }
> + fputs_unfiltered ("\n\n", gdb_stderr);
> +
> if (problem->should_dump_core == internal_problem_ask)
> {
> if (!can_dump_core (reason))
>
>
next prev parent reply other threads:[~2014-05-14 11:22 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 [this message]
2014-05-14 12:39 ` Yao Qi
2014-05-14 13:15 ` Gary Benson
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=201405141122.s4EBME4c030348@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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