From: Bob Rossi <bob@brasko.net>
To: Paul Dubuc <pdubuc@cas.org>
Cc: GDB Mailing List <gdb@sources.redhat.com>
Subject: Re: Taking the address of a convenience variable value
Date: Wed, 26 May 2004 00:00:00 -0000 [thread overview]
Message-ID: <20040525235958.GA30063@white> (raw)
In-Reply-To: <40B37A92.6020106@cas.org>
On Tue, May 25, 2004 at 12:55:46PM -0400, Paul Dubuc wrote:
> In the June 2004 issue of the C/C++ User's Journal (p. 24) there is an
> article on how to write user-defined commands for gdb to examine the
> contents of STL vectors, sets and maps. It looks extremely useful, so I
> decided to try it modifying the commands for use with the GCC STL, but I
> can't get some of the commands for sets and maps to work. It relies on a
> tecnique that involves being able to take the address of a convenience
> variable value, for example:
>
> set $maptype = &$arg0._M_t._M_header->_M_value_field
> set $maptypep = &$maptype
>
> When I try this the 2nd statement gives me the error message
>
> Attempt to take address of value not located in memory.
>
> It doesn't work with gdb 5.3 or 6.1 on Solaris. The author claims that it
> works on HP-UX, but I don't know why it would be any different.
>
> Is there a way around this? Or is there another source of user-defined
> commands that can be used to print the contents of STL containers in gdb?
> Any help would be very much appreciated.
I read that article and was wondering if it was necessary to compile the
STL with -g and not with -O2. I don't think the author mentioned it, but
how else could all of the symbols in the STL work properly with GDB?
Bob Rossi
next prev parent reply other threads:[~2004-05-26 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 16:55 Paul Dubuc
2004-05-26 0:00 ` Bob Rossi [this message]
2004-05-26 17:24 ` Andrew Cagney
2004-05-26 17:31 ` Daniel Jacobowitz
2004-05-26 18:11 ` Paul Dubuc
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=20040525235958.GA30063@white \
--to=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=pdubuc@cas.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