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, 19 Dec 2012 21:56:00 -0000	[thread overview]
Message-ID: <bug-13041-4717-kPF0Kc6xLy@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
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #8 from Tom Tromey <tromey at redhat dot com> 2012-12-19 21:56:14 UTC ---
I can definitely make this test case do something wrong-ish.

First, I removed the bad "using" and changed the line to "Top top;".
I'll attach mine in a bit.

Then I set a breakpoint in sc_module_init and ran.
(Making sure to use gdb -nx...)
Then:

(gdb) up
#1  0x0000000000400a5e in sc_module::sc_module (this=0x7fffffffe3c0)
    at pr.cc:10
10            sc_module_init();
(gdb) 
#2  0x0000000000400eda in Top::Top (this=0x7fffffffe3c0) at pr.cc:57
57        Top(){};
(gdb) p *this
$4 = {<sc_module> = {<No data fields>}, cpu = warning: can't find linker symbol
for virtual table for `CPU' value

{<tlm_bw_transport_if> = {<tlm_bw_nonblocking_transport_if> = <invalid
address>, <tlm_bw_direct_mem_if> = <invalid address>, <No data fields>},
<sc_module> = {<No data fields>}, <No data fields>}, ram = warning: can't find
linker symbol for virtual table for `RAM' value

{<sc_module> = {<No data fields>}, <tlm_fw_transport_if> =
{<tlm_fw_nonblocking_transport_if> = <invalid address>,
<tlm_blocking_transport_if> = <invalid address>, <tlm_fw_direct_mem_if> =
<invalid address>, <tlm_transport_dbg_if> = <invalid address>, <No data
fields>}, <No data fields>}}


It seems like gdb is confused by a partially-construct object.

It isn't totally clear to me whether this is related to the original
bug, but I'm reopening nonetheless.

-- 
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.


  parent reply	other threads:[~2012-12-19 21:56 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 ` [Bug mi/13041] " tromey at redhat dot com
2011-08-04  9:47 ` 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 [this message]
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-kPF0Kc6xLy@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).