public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14235] verbose RTTI message polluting traces
Date: Fri, 15 Feb 2013 21:26:00 -0000 [thread overview]
Message-ID: <bug-14235-4717-j3jyq4HAl4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14235-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14235
--- Comment #9 from Tom Tromey <tromey at redhat dot com> 2013-02-15 21:26:08 UTC ---
(In reply to comment #8)
> It isn't completely clear to me that this would work.
> For example, could there be 2 symbols with this name in different CUs?
> One in a function and one in a namespace?
Due to name mangling differences it is possible to create a file like that.
This compiles and links just fine:
q1.cc:
namespace main {
struct Z {
virtual void x();
};
};
void main::Z::x () { }
main::Z z;
int f() { return 0; }
q2.cc:
extern int f();
int main()
{
struct Z { virtual ~Z() { } };
Z z;
return f();
}
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-02-15 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 11:05 [Bug python/14235] New: " michael.meeks at suse dot com
2012-06-14 11:08 ` [Bug python/14235] " michael.meeks at suse dot com
2012-06-14 11:10 ` michael.meeks at suse dot com
2013-01-30 9:28 ` jan.kratochvil at redhat dot com
2013-01-30 9:47 ` jan.kratochvil at redhat dot com
2013-02-12 17:10 ` andre.poenitz at digia dot com
2013-02-13 10:11 ` michael.meeks at suse dot com
2013-02-13 21:02 ` tromey at redhat dot com
2013-02-15 19:19 ` tromey at redhat dot com
2013-02-15 21:26 ` tromey at redhat dot com [this message]
2013-02-16 2:29 ` tromey at redhat dot com
2013-02-25 15:36 ` muhammad_bilal at codesourcery dot com
2013-02-25 15:54 ` muhammad_bilal at codesourcery dot com
2013-02-25 16:18 ` jan.kratochvil at redhat dot com
2014-02-16 19:20 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
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=bug-14235-4717-j3jyq4HAl4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).