Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Scott Snyder <snyder@fnal.gov>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH to avoid infinite loop in cplus-dem.c on some EDG names
Date: Fri, 15 Feb 2002 15:29:00 -0000	[thread overview]
Message-ID: <yr8664ye33n.fsf@d0sgibnl1.fnal.gov> (raw)
In-Reply-To: <20020215173626.A8937@nevyn.them.org>


>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:

    Daniel> Thanks for the patch - but demangler patches need to go to
    Daniel> gcc-patches@gcc.gnu.org.  The demangler is maintained
    Daniel> outside of GDB.

Thanks --- i wasn't completely sure where was appropriate.  I've sent
another copy there.

    Daniel> Are you testing C++ support on this compiler?  I'd be
    Daniel> quite surprised if it worked - though not unpleasantly.

I've used gcc 4.18 with that compiler for quite a while.
It doesn't really understand the C++ stuff, but it works well enough
to be useful.  With gdb 5, though, i started seeing this problem
with gdb sometimes getting stuck reading in EDG symbols.
(Actually, i first reported this in sept. 99 in reference to the SGI C++
compiler; i didn't send a patch at that point though).  KAI now has their
own set of patches to gdb 5, but it would be nice to be able to do something
useful with the standard version.  (Plus, i saw this problem occur once
even in their patched version.)

thanks,
sss


      reply	other threads:[~2002-02-15 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 14:31 scott snyder
2002-02-15 14:36 ` Daniel Jacobowitz
2002-02-15 15:29   ` Scott Snyder [this message]

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=yr8664ye33n.fsf@d0sgibnl1.fnal.gov \
    --to=snyder@fnal.gov \
    --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