From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Joel Brobecker <brobecker@gnat.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA/DWARF2] Fallback unknown language to C
Date: Thu, 10 Apr 2003 18:05:00 -0000 [thread overview]
Message-ID: <16021.45908.63160.331637@localhost.redhat.com> (raw)
In-Reply-To: <20030404222511.GA18770@nevyn.them.org>
Daniel Jacobowitz writes:
> On Fri, Apr 04, 2003 at 05:22:11PM -0500, Elena Zannoni wrote:
> > Daniel Jacobowitz writes:
> > > On Tue, Mar 11, 2003 at 05:44:15PM -0800, Joel Brobecker wrote:
> > > > I am hearing the first rumors of 5.4, I think it would be nice to have
> > > > the following change in. It's a followup on a remark made in this
> > > > message:
> > > >
> > > > http://sources.redhat.com/ml/gdb/2003-02/msg00533.html
> > > >
> > > > (GDB does not work very well when the language is unknown)
> > > >
> > > > 2003-03-11 J. Brobecker <brobecker@gnat.com>
> > > >
> > > > * dwarf2read.c (set_cu_language): Fall the language back to C
> > > > if it is unsupported.
> > > >
> > > > Ok to commit?
> > >
> > > I agree with the remark, but not the method. Does anyone see an
> > > advantage to the unk_* methods calling error() instead of silently
> > > defaulting to the C versions? That seems more appropriate to me.
> > >
> > >
> >
> > I don't like too much the idea of making the unk_lang functions
> > default silently to C. These functions, in my mind, also serve as a
> > kind of error checking in case the language settings get screwed up
> > during debugging. Maybe the solution is to provide a
> > 'partial_language' set of functions which do the bare minimum.
> >
> > The thing I missed from the various postings was a real reason of why
> > the behavior changed. I guess that for stabs we didn't detect any of
> > these languages at all and we defaulted to C from
> > set_initial_language().
>
> Yeah, I think that's what was happening. If you prefer Joel's method
> I certainly don't object.
>
I would prefer to have the partial language support. Joel, any chance
you could be bribed into doing it? I think all it would be needed is
to create a new language vector and copy/rename some of the
c-functions into it.
elena
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-10 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 1:44 Joel Brobecker
2003-03-12 14:59 ` Daniel Jacobowitz
2003-04-07 13:24 ` Elena Zannoni
2003-04-04 22:25 ` Daniel Jacobowitz
2003-04-10 18:05 ` Elena Zannoni [this message]
2003-04-10 19:08 ` Joel Brobecker
2003-04-10 19:48 ` Elena Zannoni
2003-04-10 20:00 ` Joel Brobecker
2003-04-23 0:04 ` Joel Brobecker
2003-04-23 0:52 ` Elena Zannoni
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=16021.45908.63160.331637@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=brobecker@gnat.com \
--cc=drow@mvista.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