Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "B. Kosnik" <bkoz@nabi.net>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: mec@shout.net, gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ testsuite 1.3: member_data_static.exp (resend)
Date: Wed, 29 May 2002 08:34:00 -0000	[thread overview]
Message-ID: <20020529081930.325bc903.bkoz@nabi.net> (raw)
In-Reply-To: <20020529150837.GA21893@branoic.them.org>


> Compile the testcase (just -c will do).  Then run `nm' over the
> symbols.  Look for the `data' member; it isn't there.  <optimized out>
> is correct. My C++ lawyering is a little rusty, but I believe this is
> correct; it's a templated member, and not explicitly instantiated, and
> not even implicitly instantiated.  I don't see a reason for it to be
> emitted, and if it isn't emitted GDB can't help you figure out what
> its value is.

Aaah. You are correct. 

Adding:
template class __gnu_test::gnu_obj_3<long>;
template class __gnu_test::gnu_obj_2<int>;

Gives:

(gdb) p test3
$1 = {static data = {<gnu_obj_1> = {static test = true, static key1 = 5,

      static key2 = 77, static value = oriental}, _vptr.gnu_obj_2 =
0x8092fac, 
    static value_derived = etruscan}}

So, with this addition, this test case would pass, no?

-benjamin


  reply	other threads:[~2002-05-29 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 15:26 Michael Elizabeth Chastain
2002-05-29  8:09 ` Benjamin Kosnik
2002-05-29  8:19   ` Daniel Jacobowitz
2002-05-29  8:34     ` B. Kosnik [this message]
2002-05-29  9:39       ` Daniel Jacobowitz
2002-05-30  7:56         ` Benjamin Kosnik
  -- strict thread matches above, loose matches on Subject: below --
2002-05-30 12:29 Michael Elizabeth Chastain
2002-05-30 12:12 Michael Elizabeth Chastain
2002-05-29  8:34 Michael Elizabeth Chastain
2002-05-27 16:02 Michael Elizabeth Chastain
2002-05-28  9:17 ` Benjamin Kosnik
2002-05-28  9:47   ` Daniel Jacobowitz
2002-05-27  6:28 Benjamin Kosnik

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=20020529081930.325bc903.bkoz@nabi.net \
    --to=bkoz@nabi.net \
    --cc=bkoz@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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