Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite/c++] test script for PR c++/186
Date: Mon, 24 Nov 2003 16:41:00 -0000	[thread overview]
Message-ID: <20031124164141.6B5554B409@berman.michael-chastain.com> (raw)

Sigh, I have to put this patch on hold for a little while.

I was adding more tests to it and I ran into a test where
gdb really does the wrong thing with gcc 2.95.3.  That is:

  (gdb) ptype alpha
  type = class A {
    public:
      int a1;

      virtual ~A(void);
  }
  (gdb) print alpha
  $1 = {a1 = 100, _vptr.A = 0x804e198}
  (gdb) print *&alpha
  $2 = {a1 = 942760548, _vptr.A = 0x63632e36}
  (gdb) print *&alpha
  $3 = {a1 = -1073743984, _vptr.A = 0x8}
  (gdb) print *&alpha
  $4 = {a1 = -1073750008, _vptr.A = 0x2c}

I think the problem is somewhere around where gnuv2_value_rtti_type
calls lookup_typename.  Before David's big namespace patch on
2003-09-11, lookup_typename returned a TYPE_CODE_STRUCT type to
gnuv2_value_rtti_type.  Now lookup_typename is returning a
TYPE_CODE_NAMESPACE type and as you can see, gdb is printing random
weird values when it goes through gnuv2_value_rtti_type.

So I am gonna pursue that bug now, because it is simpler,
and put this patch on hold.

Michael C

===

2003-11-23  Michael Chastain  <mec.gnu@mindspring.com>

	New test case for PR c++/186.
	* gdb.cp/gdb186.cc: New file.
	* gdb.cp/gdb186.exp: New file.


             reply	other threads:[~2003-11-24 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 16:41 Michael Elizabeth Chastain [this message]
2003-11-24 17:27 ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2003-11-24 18:13 Michael Elizabeth Chastain
2003-11-24 20:02 ` 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=20031124164141.6B5554B409@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb-patches@sources.redhat.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