From: Christophe LYON <christophe.lyon@st.com>
To: gdb@sourceware.org
Subject: Re: gdb.cp/templates.exp, ctor/dtor breakpoints, etc....
Date: Mon, 19 Jan 2009 15:31:00 -0000 [thread overview]
Message-ID: <49749C97.80000@st.com> (raw)
In-Reply-To: <20090116171843.GA26829@caradoc.them.org>
On 16.01.2009 18:18, Daniel Jacobowitz wrote:
> On Fri, Jan 16, 2009 at 06:11:08PM +0100, Christophe LYON wrote:
>> Doing this, I follow GCC behaviour, but I get a regression. If we don't
>> consider this a GCC bug, it means that the way GDB recognizes ctor/dtor
>> (any probably any overloaded function) is to be revisited? Am I right?
>
> Yes, all of the name recognition stuff is broken. We shouldn't be
> relying on mangled names, since there are compilers we can not change
> as easily as GCC or yours that do not emit them.
>
Well, currently the gdb.cp/templates.exp is still KFAIL, so I guess the
decision was that GCC should not output mangled names (somewhat
confirmed by
http://gcc.gnu.org/ml/gcc/2001-12/msg00260.html).
But... if GDB does not rely on mangled names, how is it supposed to find
the right template instantiation when trying to set a breakpoint on a
function? For instance in templates.exp, where the T5 template is
defined, how to find the T5<int> ctor, if all the ctor instantiations
are named "T5" ? Should GDB analyse all the type definition in
.debug_info and find the right type?
Christophe.
next prev parent reply other threads:[~2009-01-19 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 10:20 Christophe LYON
2009-01-16 15:04 ` Daniel Jacobowitz
2009-01-16 17:12 ` Christophe LYON
2009-01-16 17:19 ` Daniel Jacobowitz
2009-01-19 15:31 ` Christophe LYON [this message]
2009-01-19 15:56 ` Daniel Jacobowitz
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=49749C97.80000@st.com \
--to=christophe.lyon@st.com \
--cc=gdb@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