From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, Kris Warkentin <kewarken@qnx.com>
Subject: Re: RFA: tweak minsyms check for GNU v3 symbols
Date: Thu, 03 Apr 2003 21:37:00 -0000 [thread overview]
Message-ID: <16012.43672.471576.171837@localhost.redhat.com> (raw)
In-Reply-To: <20030303035409.GA5850@nevyn.them.org>
Daniel Jacobowitz writes:
> This is based on a patch that Kris Warkentin sent out last October, that's
> been sitting in my inbox for a while. It's a little more efficient but the
> idea is the same. Right now, we consider any _Z symbol to imply GNU v3; but
> what we really want is for any _Z symbol _which demangled successfully_ to
> imply GNU v3. _Zero is the QNX example of a false positive for the current
> check. It's still not perfect, but it's much better.
>
> Tested in combination with the "set cp-abi" patch, to make sure it behaved
> properly; sure enough:
> - we still get GNU v3 for a v3 application
> - we no longer get GNU v3 for a v2 application containing _Zero (before
> the patch, we did).
>
> Is this OK?
>
I am back. yey.
approved, sure.
elena
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
> 2003-03-02 Daniel Jacobowitz <drow@mvista.com>
>
> * minsyms.c (install_minimal_symbols): Only switch to gnu-v3 mode
> if the linkage name demangled successfully.
>
> Index: minsyms.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/minsyms.c,v
> retrieving revision 1.26
> diff -u -p -r1.26 minsyms.c
> --- minsyms.c 25 Feb 2003 21:36:18 -0000 1.26
> +++ minsyms.c 2 Mar 2003 18:38:28 -0000
> @@ -918,8 +918,14 @@ install_minimal_symbols (struct objfile
>
> for (i = 0; i < mcount; i++)
> {
> - const char *name = DEPRECATED_SYMBOL_NAME (&objfile->msymbols[i]);
> - if (name[0] == '_' && name[1] == 'Z')
> + /* If a symbol's name starts with _Z and was successfully
> + demangled, then we can assume we've found a GNU v3 symbol.
> + For now we set the C++ ABI globally; if the user is
> + mixing ABIs then the user will need to "set cp-abi"
> + manually. */
> + const char *name = SYMBOL_LINKAGE_NAME (&objfile->msymbols[i]);
> + if (name[0] == '_' && name[1] == 'Z'
> + && SYMBOL_DEMANGLED_NAME (&objfile->msymbols[i]) != NULL)
> {
> switch_to_cp_abi ("gnu-v3");
> break;
next prev parent reply other threads:[~2003-04-03 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 3:54 Daniel Jacobowitz
2003-03-03 14:48 ` Kris Warkentin
2003-04-03 21:37 ` Elena Zannoni [this message]
2003-04-13 15:25 ` RFA: " 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=16012.43672.471576.171837@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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