From: Michael Elizabeth Chastain <mec@shout.net>
To: eliz@is.elta.co.il
Cc: gdb@sources.redhat.com, sassi@uni.de
Subject: Re: GDB C++ support
Date: Tue, 15 Jan 2002 09:48:00 -0000 [thread overview]
Message-ID: <200201151748.LAA16445@duracef.shout.net> (raw)
eli> You don't need to apologize about not having the information I asked
eli> for. But there's no need to be harsh, either.
Yeah, you're right, I got up grouchy this morning. I apologize for that.
Co-incidentally, I'm making test runs with stock 5.1 right now.
Here's an excerpt from gdb.log:
# gdb 5.1, gcc 3.0.2, -gdwarf-2, gdb.c++/method.exp
(gdb) break main^M
Breakpoint 1 at 0x8048549: file /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc, line 66.^M
(gdb) run ^M
Starting program: /berman/migchain/build/native/gdb-5.1/gdb/testsuite/gdb.c++/method ^M
^M
Breakpoint 1, main () at /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc:66^M
66 k = 10;^M
(gdb) break A::foo^M
Breakpoint 2 at 0x80484a6: file /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc, line 38.^M
(gdb) PASS: gdb.c++/method.exp: set breakpoint on A::foo
continue^M
Continuing.^M
^M
Breakpoint 2, A::foo(int) (this=0xbffff0e0, arg=13) at /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc:38^M
38 x += arg;^M
(gdb) FAIL: gdb.c++/method.exp: continuing and breaking in A::foo
So you can see that 'break A::foo' works and gdb takes the breakpoint.
I don't know what that "FAIL" is about (that is a different issue).
Constructively,
Michael C
next reply other threads:[~2002-01-15 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 9:48 Michael Elizabeth Chastain [this message]
2002-01-15 10:00 ` Eli Zaretskii
2002-01-15 10:14 ` Daniel Jacobowitz
[not found] <1011102697.16058.ezmlm@sources.redhat.com>
2002-01-15 13:08 ` Jim Ingham
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 5:57 Michael Elizabeth Chastain
2002-01-15 9:15 ` Eli Zaretskii
2002-01-14 10:40 Michael Elizabeth Chastain
2002-01-14 23:43 ` Eli Zaretskii
2002-01-14 10:25 Guido S.
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=200201151748.LAA16445@duracef.shout.net \
--to=mec@shout.net \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=sassi@uni.de \
/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