From: Daniel Berlin <dberlin@dberlin.org>
To: "Jacques Le Normand" <jacqueslen@sympatico.ca>
Cc: <gdb@sources.redhat.com>
Subject: Re: *****SPAM***** casting in gdb
Date: Fri, 13 Dec 2002 07:33:00 -0000 [thread overview]
Message-ID: <2ADB5EBD-0EB0-11D7-8880-000393575BCC@dberlin.org> (raw)
In-Reply-To: <002301c2a270$e82f3540$c11ffea9@ehville>
On Friday, December 13, 2002, at 01:28 AM, Jacques Le Normand wrote:
> how do you get gdb to cast to size_t?
> I realize that size_t is a typedef to unsigned long long or somesuch.
> A little background:
> when I'm debugging my vector<int> v, gdb won't let me type v[0],
> instead =
> it says this: "One of the arguments you tried to pass to operator[] =
> could not be converted to what the funtion wants."
> I then looked up what operator[] took in the sgi docs and it said a =
> size_t. Anyone have any ideas?
> (I realize I can do p *(v._M_start+n) , but having a method for
> casting =
> would help me later on)
> --Jacques
>
While this doesn't help *you*, it should help the current C++ people
for GDB:
I've seen this with STABS debugging info when some of the operator
functions were left out of the debugging info, but others weren't (GCC
+ STABS will omit unused functions from debug info), and we ommitted
the operator we really need to use, and in some cases when we parsed
the types of the arguments out of the demangled function name and come
up with some weird type.
>
next prev parent reply other threads:[~2002-12-13 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 12:22 dejagnu bemis
2002-11-20 20:37 ` dejagnu Andrew Cagney
2002-12-05 16:26 ` dejagnu Fernando Nasser
2002-12-05 16:58 ` dejagnu bemis
2002-12-05 17:08 ` dejagnu Fernando Nasser
2002-12-12 22:26 ` dejagnu Rob Savoye
2002-12-12 22:29 ` casting in gdb Jacques Le Normand
2002-12-13 7:33 ` Daniel Berlin [this message]
2002-12-13 8:46 ` *****SPAM***** " Daniel Jacobowitz
2002-12-13 11:43 ` Jacques Le Normand
2002-12-13 23:34 ` Daniel Jacobowitz
2002-12-14 11:55 ` Daniel Berlin
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=2ADB5EBD-0EB0-11D7-8880-000393575BCC@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gdb@sources.redhat.com \
--cc=jacqueslen@sympatico.ca \
/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