From: Hui Zhu <teawater@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches ml <gdb-patches@sourceware.org>,
Tristan Gingold <gingold@adacore.com>,
Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [RFA] Show some tips when file cmd get bfd_error_file_ambiguously_recognized
Date: Tue, 26 Jan 2010 08:01:00 -0000 [thread overview]
Message-ID: <daef60381001260001j7dfb4c09jdace41e666a1b0a1@mail.gmail.com> (raw)
In-Reply-To: <daef60381001190008x3e2964d2h6439db9293e3b3e6@mail.gmail.com>
About this patch. There are a lot of function call "bfd_check_format".
What about add a wrapper of "bfd_check_format_matches" to gdb. This
wrapper call "bfd_check_format_matches" and if it get
bfd_error_file_ambiguously_recognized, output the format and other
help message before it return.
Change the "bfd_check_format" to the wrapper.
Then when gdb get bfd_error_file_ambiguously_recognized, putput the
help message directly.
What do you think about it?
Thanks,
Hui
On Tue, Jan 19, 2010 at 16:08, Hui Zhu <teawater@gmail.com> wrote:
>>
>>> + fprintf_filtered (gdb_stderr, _("It matchs formats:"));
>>
>> "matches"
>>
>
> Fixed.
>
> Thanks,
> Hui
>
> 2010-01-19 Hui Zhu <teawater@gmail.com>
>
> * exec.c (exec_file_attach): Output some tips when
> bfd_get_error is bfd_error_file_ambiguously_recognized.
>
next prev parent reply other threads:[~2010-01-26 8:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 2:44 Hui Zhu
2010-01-14 10:15 ` Jan Kratochvil
2010-01-19 7:01 ` Hui Zhu
2010-01-19 7:57 ` Jan Kratochvil
2010-01-19 8:08 ` Hui Zhu
2010-01-26 8:01 ` Hui Zhu [this message]
2010-01-26 21:04 ` Doug Evans
2010-01-27 9:01 ` Hui Zhu
2010-01-28 18:18 ` Doug Evans
2010-01-28 21:56 ` Jan Kratochvil
2010-01-28 21:59 ` Doug Evans
2010-01-29 3:51 ` Joel Brobecker
2010-01-29 9:06 ` Hui Zhu
2010-02-04 7:09 ` Hui Zhu
2010-02-04 17:38 ` Doug Evans
2010-02-05 2:44 ` Hui Zhu
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=daef60381001260001j7dfb4c09jdace41e666a1b0a1@mail.gmail.com \
--to=teawater@gmail.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=jan.kratochvil@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