From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Set current language when dumping symtab
Date: Sun, 29 May 2005 00:09:00 -0000 [thread overview]
Message-ID: <20050528234905.GF22435@nevyn.them.org> (raw)
In-Reply-To: <20050504001955.GE2439@adacore.com>
On Tue, May 03, 2005 at 05:19:55PM -0700, Joel Brobecker wrote:
> Hello,
>
> One of our users tried to use the "maint print symbols syms" command
> to dump all the symbols in a text format, and that caused a crash on
> x86-windows. The reason for the crash is that dump_symtab() indirectly
> uses the current language vector to analyze the symbols and then do
> the printing. The symtab language may be different from the current
> language, so the current language needs to be temporarily adjusted
> during the printing. This is what the attached patch does.
>
> 2005-05-02 Joel Brobecker <brobecker@adacore.com>
>
> * symmisc.c (dump_symtab_1): Renamed from dump_symtab.
> (dump_symtab): New function.
> * Makefile.in (symmisc.o): Add dependency on ui-out.h.
What's the new dependency on ui-out.h for? I didn't see anything
obvious in the patch.
Also, what crashes? i.e. why specifically is it harmful to have the
wrong language set?
Also, I am not convinced that the new TRY_CATCH is necessary. The
only bit likely to throw is print_symbol, which is already wrapped in
catch_errors.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-28 23:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 0:20 Joel Brobecker
2005-05-29 0:09 ` Daniel Jacobowitz [this message]
2005-05-29 2:54 ` Joel Brobecker
2005-05-29 2:57 ` Daniel Jacobowitz
2005-05-30 15:59 ` Joel Brobecker
2005-05-30 19:55 ` Joel Brobecker
2005-05-30 20:06 ` Daniel Jacobowitz
2005-06-01 1:29 ` Joel Brobecker
2005-06-01 2:00 ` Daniel Jacobowitz
2005-06-03 0:10 ` Joel Brobecker
2005-06-03 19:14 ` Daniel Jacobowitz
2005-06-03 23:27 ` Joel Brobecker
2005-06-02 16:54 ` Joel Brobecker
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=20050528234905.GF22435@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.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