From: "Jacques Le Normand" <jacqueslen@sympatico.ca>
To: <gdb@sources.redhat.com>
Subject: casting in gdb
Date: Sat, 14 Dec 2002 19:49:00 -0000 [thread overview]
Message-ID: <002201c2a3ed$02a1f3e0$0100a8c0@ehville> (raw)
That explains alot, thanks
Would you know how to tell g++ to keep all the methods, even when they're
not used?
Say I have a map<string,int> m, how would I get gdb to display m["foo"] ?
It
gives me the silly "function expects something else" error, which I can
understand since gdb won't cast from char* to string. I'm guessing I need
to
define my own subroutines.
--Jacques
> ----- Original Message -----
> From: "Daniel Jacobowitz" <drow@mvista.com>
> To: "Jacques Le Normand" <jacqueslen@sympatico.ca>
> Cc: "Daniel Berlin" <dberlin@dberlin.org>; <gdb@sources.redhat.com>
> Sent: Saturday, December 14, 2002 2:35 AM
> Subject: Re: casting in gdb
>
>
> > On Fri, Dec 13, 2002 at 02:43:17PM -0500, Jacques Le Normand wrote:
> > > here you go, thanks for lending a hand...
> > >
> > > [countchocula@chocoland countchocula]$ g++ -ggdb test.cpp -o test.o
> > > [countchocula@chocoland countchocula]$ gdb test.o
> > > GNU gdb Red Hat Linux (5.2.1-4)
> > > Copyright 2002 Free Software Foundation, Inc.
> > > GDB is free software, covered by the GNU General Public License, and
you
> are
> > > welcome to change it and/or distribute copies of it under certain
> > > conditions.
> > > Type "show copying" to see the conditions.
> > > There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> > > This GDB was configured as "i386-redhat-linux"...
> > > (gdb) b 10
> > > Breakpoint 1 at 0x80486f5: file test.cpp, line 10.
> > > (gdb) r
> > > Starting program: /home/countchocula/test.o
> > >
> > > Breakpoint 1, main () at test.cpp:10
> > > 10 a.push_back(2);
> > > (gdb) p a[0]
> > > One of the arguments you tried to pass to operator[] could not be
> converted
> > > to w
> > > hat the function wants.
> > > (gdb)
> >
> > This one's pretty simple once you figure it out. The error message is
> > really bad; I'll hold on to this and try to improve it.
> >
> > Your program doesn't _use_ operator[]. So it doesn't get compiled into
> > the program, and GDB can't call it to figure out what to do.
> >
> > What happens if you add a call to the operator?
> >
> > [I noticed some other quirks; for instance, if your program only uses
> > the mutable version and GDB finds the const version first, it may get
> > confused...]
> >
> > --
> > Daniel Jacobowitz
> > MontaVista Software Debian GNU/Linux Developer
> >
>
next reply other threads:[~2002-12-15 3:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 19:49 Jacques Le Normand [this message]
2002-12-14 19:59 ` Daniel Jacobowitz
[not found] <1042721692.8268.ezmlm@sources.redhat.com>
2003-01-16 18:53 ` Jim Ingham
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 21:47 Michael Elizabeth Chastain
2002-12-14 22:48 ` Jacques Le Normand
2002-12-15 8:05 ` Daniel Jacobowitz
2003-01-15 18:47 ` David Carlton
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 ` *****SPAM***** " Daniel Berlin
2002-12-13 8:46 ` 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='002201c2a3ed$02a1f3e0$0100a8c0@ehville' \
--to=jacqueslen@sympatico.ca \
--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