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 mi/13041] Virtual base class botch
Date: Wed, 03 Aug 2011 20:37:00 -0000 [thread overview]
Message-ID: <bug-13041-4717-8zSNitMgCA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13041-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13041
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2011-08-03 20:36:39 UTC ---
It would be most helpful if you could construct a simple,
self-contained test case so we can reproduce the bug.
Your compiler info probably also matters.
If you can't do this, then maybe some more info from debugging
gdb itself would be useful. That is really not as good though.
--
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:[~2011-08-03 20:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 8:11 [Bug mi/13041] New: " dj170590 at hotmail dot com
2011-08-03 20:37 ` tromey at redhat dot com [this message]
2011-08-04 9:47 ` [Bug mi/13041] " pedro at codesourcery dot com
2011-08-04 9:48 ` pedro at codesourcery dot com
2011-08-04 10:42 ` dj170590 at hotmail dot com
2011-08-04 14:10 ` pedro at codesourcery dot com
2011-08-04 15:04 ` dj170590 at hotmail dot com
2011-08-04 15:30 ` dj170590 at hotmail dot com
2011-08-04 15:56 ` pedro at codesourcery dot com
2012-12-19 21:56 ` tromey at redhat dot com
2012-12-19 21:58 ` tromey at redhat dot com
2022-08-10 17:09 ` [Bug c++/13041] " tromey 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-13041-4717-8zSNitMgCA@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).