From: Carlo Wood <carlo@alinoe.com>
To: gdb@sources.redhat.com
Subject: Re: gdb bugs showing while working on libcwd
Date: Tue, 28 May 2002 05:50:00 -0000 [thread overview]
Message-ID: <20020528145020.A17748@alinoe.com> (raw)
In-Reply-To: <20020528081656.GB5390@branoic.them.org>; from drow@mvista.com on Tue, May 28, 2002 at 04:16:56AM -0400
On Tue, May 28, 2002 at 04:16:56AM -0400, Daniel Jacobowitz wrote:
> By the way, if that includes a v3 demangler - there are three failures
> in the demangler testsuite on v3 for functions taking function pointers
> that I can't wrap my head around... :)
Would replacing __cxa_demangle in libiberty with a demangler
that does v3 demangling (and only v3 demangling) do the job?
I am not familiar with this libiberty interface that seems
to support a dozen different mangling styles.
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2002-05-28 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020522115242.C28512@redhat.com>
[not found] ` <20020523153816.A4454@alinoe.com>
[not found] ` <20020523094527.B25730@redhat.com>
2002-05-23 17:35 ` Carlo Wood
2002-05-23 18:58 ` Daniel Jacobowitz
2002-05-24 8:41 ` Huge problems with debugging threaded C++ programs Liam Stewart
2002-05-24 9:42 ` gdb bugs showing while working on libcwd Carlo Wood
2002-05-24 18:33 ` Carlo Wood
2002-05-24 18:41 ` Daniel Jacobowitz
2002-05-26 18:43 ` Carlo Wood
2002-05-26 23:03 ` Daniel Jacobowitz
2002-05-27 5:42 ` Carlo Wood
2002-05-27 11:05 ` Daniel Jacobowitz
2002-05-27 17:01 ` Carlo Wood
2002-05-28 1:17 ` Daniel Jacobowitz
2002-05-28 5:50 ` Carlo Wood [this message]
2002-05-28 10:37 ` Daniel Jacobowitz
2002-05-28 15:54 ` Carlo Wood
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=20020528145020.A17748@alinoe.com \
--to=carlo@alinoe.com \
--cc=gdb@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