From: Maik Beckmann <maikbeckmann@gmx.de>
To: gdb@sourceware.org
Subject: Re: how to view content in stl vector
Date: Mon, 18 Jun 2007 14:57:00 -0000 [thread overview]
Message-ID: <200706181657.05961.maikbeckmann@gmx.de> (raw)
In-Reply-To: <20070618144438.GA22051@caradoc.them.org>
Am Montag, 18. Juni 2007 16:44:38 schrieb Daniel Jacobowitz:
> I don't know. It may just be broken. I did provoke an amusing
> internal error trying to get it to work...
>
> (gdb) p 'int f<int>'()
> /space/debian/gdb/build-area/gdb-6.6.dfsg/gdb/valops.c:2112:
> internal-error: find_oload_champ_namespace_loop: Assertion
> `new_oload_champ != -1' failed.
> A problem internal to GDB has been detected,
This works:
1. start and run gdb:
2.look for the matching disassembly line
0x08048972 <main+30>: call 0x8048b66 <_Z3fooIiEbT_>
3. let gdb say what it has to say:
output _Z3fooIiEbT_
{bool (int)} 0x8048b66 <bool foo<int>(int)>
4. call it like this:
p ({bool (int)} 0x8048b66)(i)
$1 = true
The gdb-bug causes one extra step.
However, as far as I understand it should be possible to wrap this and the
typename-storing stuff into convenience functions, if your plan to get
python into gdb-business succeeds.
many thanks to you Daniel,
Maik Beckmann
next prev parent reply other threads:[~2007-06-18 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 15:05 kdsfinger
2007-06-15 19:52 ` Mark Kettenis
2007-06-18 8:53 ` Alpár Jüttner
2007-06-18 11:15 ` Maik Beckmann
2007-06-18 11:27 ` Daniel Jacobowitz
2007-06-18 12:27 ` Maik Beckmann
2007-06-18 12:36 ` Daniel Jacobowitz
2007-06-18 12:54 ` Maik Beckmann
2007-06-18 13:06 ` Daniel Jacobowitz
2007-06-18 14:35 ` Maik Beckmann
2007-06-18 14:44 ` Daniel Jacobowitz
2007-06-18 14:57 ` Maik Beckmann [this message]
2007-06-18 15:03 ` Maik Beckmann
2007-06-18 15:28 ` Andreas Schwab
2007-06-18 15:49 ` Maik Beckmann
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=200706181657.05961.maikbeckmann@gmx.de \
--to=maikbeckmann@gmx.de \
--cc=gdb@sourceware.org \
/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