From: Daedalus <daedalus@projecticarus.com>
To: gdb@sources.redhat.com
Subject: Re: Is Single step into C++ virtual thunk still broken?
Date: Tue, 09 Jul 2002 14:14:00 -0000 [thread overview]
Message-ID: <1026249182.10774.3.camel@mojo> (raw)
On Tue, 2002-07-09 at 21:20, Daniel Jacobowitz wrote:
>
> Does this persist if you use -static? If so, please give me:
> thunk.o (compile using g++ -g3 -c thunk.cpp)
> thunk (compile using g++ -g3 -o thunk thunk.o -static)
>
> and I'll see if I can figure out what's going wrong. I doubt I can
run
> RH7.3 dynamically linked libraries.
>
Sure does:
[daedalus@mojo thunk]$ g++ -g3 -c thunk.cpp
[daedalus@mojo thunk]$ ls
thunk.cpp thunk.o
[daedalus@mojo thunk]$ g++ -g3 -o thunk thunk.o -static
[daedalus@mojo thunk]$ ls
thunk thunk.cpp thunk.o
[daedalus@mojo thunk]$ gdb ./thunk
GNU gdb 2002-07-09-cvs
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 "i686-pc-linux-gnu"...
(gdb) b 50
Breakpoint 1 at 0x804825e: file thunk.cpp, line 50.
(gdb) r
Starting program: /home/daedalus/src/thunk/thunk
Breakpoint 1, main (argc=1, argv=0xbffff9f4) at thunk.cpp:50
50 p->VirtualFn();
(gdb) s
virtual thunk to Derived::VirtualFn() () at thunk.cpp:43
43 }
(gdb) s
main (argc=1, argv=0xbffff9f4) at thunk.cpp:51
51 return 0;
(gdb)
Files attached
Andrew Walrond
next reply other threads:[~2002-07-09 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 14:14 Daedalus [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 8:56 Daedalus
2002-07-09 9:27 ` Daniel Jacobowitz
2002-07-09 11:44 ` Daedalus
2002-07-09 11:51 ` Daniel Jacobowitz
2002-07-09 13:10 ` Daedalus
[not found] ` <20020709202005.GA23405@nevyn.them.org>
2002-07-09 16:13 ` Daedalus
2002-07-08 6:47 Daedalus
2002-07-08 6:52 ` Daniel Jacobowitz
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=1026249182.10774.3.camel@mojo \
--to=daedalus@projecticarus.com \
--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