Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: fnf@ninemoons.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] temporary fix for bogus language check
Date: Sun, 25 Nov 2001 23:56:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1011126095535.10629G-100000@is> (raw)
Message-ID: <20011125235600.VLlc3OSha0Z_38NoutVS7KBHVaI9EMqd6eZgKKSS4RE@z> (raw)
In-Reply-To: <200111251921.fAPJLP323371@fishpond.ninemoons.com>

On Sun, 25 Nov 2001, Fred Fish wrote:


> We could fix this problem by
> eliminating the test of the current language, but then every gdb
> session would incur the additional overhead of attempting to demangle
> every symbol regardless of whether or not any C++ symbols were
> present.  Another option is to set some global flag whenever symbols
> for a C++ function are read in, and then do the current language test
> unconditionally once we know that there might be C++ symbols
> somewhere.  Yet another option is to add a parameter to lookup_symbol
> that says whether to consider the possibility that the symbol to be
> looked up is a C++ symbol, set that appropriately when calling
> lookup_symbol, and use that value to decide whether or not to try
> demangling the symbol.

I think we should consider all the languages used in the program being
debugged.  How to find out what those languages are and whether to
cache them in some list is an implementation detail.


  parent reply	other threads:[~2001-11-25 23:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25 11:26 Fred Fish
2001-11-11  4:26 ` Fred Fish
2001-11-11 10:50 ` Eli Zaretskii [this message]
2001-11-25 23:56   ` Eli Zaretskii
2001-11-12 11:34 ` Elena Zannoni
2001-11-26  9:47   ` Elena Zannoni
2001-11-25 11:53 ` Daniel Berlin
2001-11-11  8:42   ` Daniel Berlin

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=Pine.SUN.3.91.1011126095535.10629G-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=fnf@ninemoons.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