From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: gnu-v3-abi.c: problems w/ virtual base class
Date: Wed, 30 Oct 2002 11:00:00 -0000 [thread overview]
Message-ID: <20021030190128.GA21129@nevyn.them.org> (raw)
In-Reply-To: <123101c28044$f5386340$d8020c0a@catdog>
On Wed, Oct 30, 2002 at 01:48:37PM -0500, Kris Warkentin wrote:
> > > > objdump -x foo | grep _Z gave me nothing. You say there's an
> autodetect
> > > > routine? I'll have to look at it to see why it thinks we're gnu-v3 I
> > > > suppose.
> > >
> > > It's in minsyms.c:install_minimal_symbols. Hmm, does a breakpoint on
> > > switch_to_cp_abi turn up anything?
> >
> > Odd. According to that, it switched to gnu-v2. And it worked properly.
> > What the heck is going on here? I just reproduced this from the PR about
> 2
> > minutes ago and now I'm not seeing it. AAARGH!!!
> >
> > Sorry Daniel. I'm obviously losing my mind here so now I have to go back
> > and reproduce it again. *sigh*
>
> Okay, I'm seeing it in the Neutrino hosted gdb, not Windows hosted. That's
> the problem with 4 hosts and 5 targets...:-P
>
> I found the naughtiness. auto_solib_add is true on Neutrino but not on
> Windows. Guess who defines _Zero in their libc? We do!!
>
> Doh.
>
> Thanks for the help.
OK, that's the problem. What we should probably be doing in minsyms.c
is checking for a valid v3 mangled name...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-30 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 9:10 Kris Warkentin
2002-10-30 9:20 ` Daniel Jacobowitz
2002-10-30 9:30 ` Kris Warkentin
2002-10-30 9:34 ` Daniel Jacobowitz
2002-10-30 9:46 ` Kris Warkentin
2002-10-30 10:48 ` Kris Warkentin
2002-10-30 11:00 ` Daniel Jacobowitz [this message]
2002-10-30 11:19 ` Kris Warkentin
2002-10-30 11:26 ` Daniel Jacobowitz
2002-10-30 11:59 ` Kris Warkentin
2002-10-30 11:00 ` Kris Warkentin
2002-10-30 11:07 ` 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=20021030190128.GA21129@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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