From: Keith Seitz <keiths@redhat.com>
To: L P <plm@iname.com>
Cc: insight@sources.redhat.com
Subject: Re: Class not displayed in watch window (Bug?)
Date: Mon, 27 Oct 2003 18:28:00 -0000 [thread overview]
Message-ID: <3F9D71D6.2030905@redhat.com> (raw)
In-Reply-To: <20031026165251.72274.qmail@iname.com>
L P wrote:
> Hello,
> I have a class template with 2 parameters of types ( <type1,type2>).
> When I put an object of this class into watch window or into local vars window, the name is placed and the line looks like:
> Name Value
> MyObj class MyClass<int,short> {...}
> and there is no '+' sign for extension. All attempts to click on it do nothing.
>
> Meanwhile, when I type 'print MyObj' in the console window, I receive a printout of all members of MyClass.
> How can I have MyObj be shown in Watch Window?
>
> A lot of thanks ahead.
>
That sounds like a varobj bug. Try doing the same thing with MI (which I
am very certain will also fail), and then file a bug against gdb/varobj.
Keith
prev parent reply other threads:[~2003-10-27 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 16:52 L P
2003-10-27 18:28 ` Keith Seitz [this message]
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=3F9D71D6.2030905@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=plm@iname.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).