Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 17:27:00 -0000	[thread overview]
Message-ID: <yf2ad6l1xt5.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031124164141.6B5554B409@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 24 Nov 2003 11:41:41 -0500 (EST)")

On Mon, 24 Nov 2003 11:41:41 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:

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

What??  That's bizarre; I'll have to look into that one.

David Carlton
carlton@kealia.com


  reply	other threads:[~2003-11-24 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 16:41 Michael Elizabeth Chastain
2003-11-24 17:27 ` David Carlton [this message]
  -- 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=yf2ad6l1xt5.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