From: Hui Zhu <teawater@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] print a more useful error message for "gdb core"
Date: Thu, 21 Jan 2010 02:33:00 -0000 [thread overview]
Message-ID: <daef60381001201833y4e59edafh1f82642727750f03@mail.gmail.com> (raw)
In-Reply-To: <e394668d1001201612w3ddb2eebnc3ca4c36b9af7378@mail.gmail.com>
Hello,
If you don't mind, I suggest change bfd_check_format to
bfd_check_format_matches like
http://sourceware.org/ml/gdb-patches/2010-01/msg00468.html
It will give user more help when he got bfd_error_file_ambiguously_recognized.
Thanks,
Hui
On Thu, Jan 21, 2010 at 08:12, Doug Evans <dje@google.com> wrote:
> On Wed, Jan 20, 2010 at 3:56 PM, Doug Evans <dje@google.com> wrote:
>> Hi.
>>
>> If the user accidentally does "gdb core" gdb currently prints:
>>
>> "/foo/bar": not in executable format: File format not recognized
>>
>> This patch prints a more useful error message for this particular case:
>>
>> "/foo/bar" is a core file.
>> Please specify an executable to debug.
>>
>> I will check this in in a few days if there are no objections.
>
> As noted in irc, the joys of working between multiple trees.
> The previous patch didn't call exec_close.
>
> Here's an updated patch.
>
> 2010-01-20 Doug Evans <dje@google.com>
>
> * exec.c (exec_file_attach): Print a more useful error message if the
> user did "gdb core".
>
> Index: exec.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/exec.c,v
> retrieving revision 1.95
> diff -u -p -r1.95 exec.c
> --- exec.c 19 Jan 2010 09:47:47 -0000 1.95
> +++ exec.c 21 Jan 2010 00:10:17 -0000
> @@ -253,6 +253,18 @@ exec_file_attach (char *filename, int fr
> scratch_pathname = xstrdup (scratch_pathname);
> cleanups = make_cleanup (xfree, scratch_pathname);
>
> + /* If the user accidentally did "gdb core", print a useful
> + error message. */
> + if (bfd_check_format (exec_bfd, bfd_core))
> + {
> + /* Make sure to close exec_bfd, or else "run" might try to use
> + it. */
> + exec_close ();
> + error (_("\"%s\" is a core file.\n"
> + "Please specify an executable to debug."),
> + scratch_pathname);
> + }
> +
> if (!bfd_check_format (exec_bfd, bfd_object))
> {
> /* Make sure to close exec_bfd, or else "run" might try to use
>
next prev parent reply other threads:[~2010-01-21 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 23:56 Doug Evans
2010-01-21 0:13 ` Doug Evans
2010-01-21 2:33 ` Hui Zhu [this message]
2010-01-21 13:58 ` Jan Kratochvil
2010-01-21 16:34 ` Tom Tromey
2010-01-21 17:17 ` Doug Evans
2010-01-25 4:22 ` Jan Kratochvil
2010-01-28 21:37 ` Jan Kratochvil
2010-01-28 21:39 ` Doug Evans
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=daef60381001201833y4e59edafh1f82642727750f03@mail.gmail.com \
--to=teawater@gmail.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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