From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix printing frame arguments for COFF debug info
Date: Thu, 21 May 2009 03:22:00 -0000 [thread overview]
Message-ID: <837i0bp2bb.fsf@gnu.org> (raw)
In-Reply-To: <20090520213200.GE16152@adacore.com>
> Date: Wed, 20 May 2009 14:32:00 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > The first step towards solving this is to fix coffread.c, as in the
> > patch I suggest below. OK to commit it?
>
> > 2009-05-16 Eli Zaretskii <eliz@gnu.org>
> >
> > * coffread.c (process_coff_symbol): Set the symbol's language to
> > the language of current_subfile.
>
> That seems like a sensible change, and it is something we also do
> in the stabs reader, so I'd say this is OK.
Thanks.
> > Even if this patch is accepted, I'm not sure that's all we need to do.
> > At least minsyms.c:prim_record_minimal_symbol_and_info also sets the
> > symbol's language to language_auto. Should we make sure neither
> > common_val_print nor val_print ever get language_auto as the language?
> > That is, should we fall back to current_language in that case?
>
> I see that this is addressed in one of your followup messages
Not really, no. The followup messages deal with a different problem.
This issue, i.e. whether common_val_print and/or val_print should be
defensive about getting language_auto, still remains. I'd like to
hear your opinion about that.
next prev parent reply other threads:[~2009-05-21 3:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 16:51 Eli Zaretskii
2009-05-16 18:00 ` More problems with language in printing symbols Eli Zaretskii
2009-05-17 16:17 ` [RFA] " Eli Zaretskii
2009-05-20 23:07 ` Joel Brobecker
2009-05-23 9:26 ` Eli Zaretskii
2009-05-20 23:07 ` [RFA] Fix printing frame arguments for COFF debug info Joel Brobecker
2009-05-21 3:22 ` Eli Zaretskii [this message]
2009-05-21 17:05 ` Joel Brobecker
2009-05-23 10:37 ` Eli Zaretskii
2009-05-25 6:29 ` Joel Brobecker
2009-05-25 20:41 ` Eli Zaretskii
2009-05-25 22:55 ` Joel Brobecker
2009-05-29 12:07 ` Eli Zaretskii
2009-05-23 9:33 ` Eli Zaretskii
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=837i0bp2bb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.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