From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite/c++] test script for PR c++/186
Date: Mon, 24 Nov 2003 20:02:00 -0000 [thread overview]
Message-ID: <yf2y8u5y1pe.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031124181321.4AF214B409@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 24 Nov 2003 13:13:21 -0500 (EST)")
On Mon, 24 Nov 2003 13:13:21 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:
> But beyond that level, gdb is printing bogus values. Specifically:
> I've got these two classes, "A" and "B". "B" is derived from "A".
> I've got an object that used to be a "B", but thanks to B::~B, the
> dynamic type is actually "A" by now. When I say "print *pb", gdb
> prints values for the fields of B. But it prints bogus data, and it
> prints *different* bogus data on successive calls. It's not like
> gdb is choosing an infelicitous type and forcing the target memory
> into that type, it's like gdb is dereferencing wild pointers
> internally.
Right, gotcha. That's bad.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-11-24 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 18:13 Michael Elizabeth Chastain
2003-11-24 20:02 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-24 16:41 Michael Elizabeth Chastain
2003-11-24 17:27 ` David Carlton
2003-11-23 23:00 Michael Elizabeth Chastain
2003-11-24 17:25 ` David Carlton
2003-11-23 22:05 Michael Elizabeth Chastain
2003-11-23 22:08 ` Daniel Jacobowitz
2003-11-23 22:22 ` Daniel Jacobowitz
2003-11-24 17:23 ` David Carlton
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=yf2y8u5y1pe.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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