From: Daedalus <daedalus@projecticarus.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Is Single step into C++ virtual thunk still broken?
Date: Tue, 09 Jul 2002 16:13:00 -0000 [thread overview]
Message-ID: <1026256318.10599.2.camel@mojo> (raw)
In-Reply-To: <20020709202005.GA23405@nevyn.them.org>
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.
>
FYI, I tried the latest cvs version of gcc 3.2, and got the same
results.
Andrew Walrond
next prev parent reply other threads:[~2002-07-09 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 14:14 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=1026256318.10599.2.camel@mojo \
--to=daedalus@projecticarus.com \
--cc=drow@false.org \
--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