Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: note that minsyms can have duplicate demangled names
Date: Mon, 20 Sep 2004 16:55:00 -0000	[thread overview]
Message-ID: <vt2d60gop91.fsf@zenia.home> (raw)


2004-09-19  Jim Blandy  <jimb@redhat.com>

	* minsyms.c (lookup_minimal_symbol): Doc fix.

Index: gdb/minsyms.c
===================================================================
RCS file: /cvs/src/src/gdb/minsyms.c,v
retrieving revision 1.43
diff -c -p -r1.43 minsyms.c
*** gdb/minsyms.c	20 May 2004 09:51:33 -0000	1.43
--- gdb/minsyms.c	20 Sep 2004 00:50:38 -0000
*************** add_minsym_to_demangled_hash_table (stru
*** 145,151 ****
     Note:  One instance where there may be duplicate minimal symbols with
     the same name is when the symbol tables for a shared library and the
     symbol tables for an executable contain global symbols with the same
!    names (the dynamic linker deals with the duplication).  */
  
  struct minimal_symbol *
  lookup_minimal_symbol (const char *name, const char *sfile,
--- 145,159 ----
     Note:  One instance where there may be duplicate minimal symbols with
     the same name is when the symbol tables for a shared library and the
     symbol tables for an executable contain global symbols with the same
!    names (the dynamic linker deals with the duplication).
! 
!    It's also possible to have minimal symbols with different mangled
!    names, but identical demangled names.  For example, the GNU C++ v3
!    ABI requires the generation of two (or perhaps three) copies of
!    constructor functions --- "in-charge", "not-in-charge", and
!    "allocate" copies; destructors may be duplicated as well.
!    Obviously, there must be distinct mangled names for each of these,
!    but the demangled names are all the same: S::S or S::~S.  */
  
  struct minimal_symbol *
  lookup_minimal_symbol (const char *name, const char *sfile,


                 reply	other threads:[~2004-09-20 16:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=vt2d60gop91.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@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