From: Tom Tromey <tromey@redhat.com>
To: "André Pönitz" <apoenitz@trolltech.com>
Cc: gdb@sources.redhat.com
Subject: Re: std::string and MI
Date: Tue, 02 Dec 2008 17:37:00 -0000 [thread overview]
Message-ID: <m3r64qcwc1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200811271339.03070.apoenitz@trolltech.com> (=?utf-8?Q?=22And?= =?utf-8?Q?r=C3=A9_P=C3=B6nitz=22's?= message of "Thu\, 27 Nov 2008 13\:38\:56 +0100")
>>>>> "André" == André Pönitz <apoenitz@trolltech.com> writes:
[...]
André> In both cases the 'std::' namespace is missing from the type.
André> As the "namespace foo" example above shows, this can't be the general
André> problem with namespaces, as "foo::string" is reported as I expected.
André> Does anybody know how to tweak gdb's settings so that it produces the
André> std:: namespace, too?
I didn't look at this example, but in other cases where "whatis"
printed something odd, I have tracked the problem down to weird debug
info. You might take a look at that. IOW, it may not be gdb's
decision. There's a GCC PR or two in this area.
Tom
next prev parent reply other threads:[~2008-12-02 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 12:39 André Pönitz
2008-12-02 17:37 ` Tom Tromey [this message]
2008-12-03 17:27 ` Daniel Jacobowitz
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=m3r64qcwc1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=apoenitz@trolltech.com \
--cc=gdb@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