aboutsummaryrefslogtreecommitdiff
path: root/gdb/minsyms.c
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2004-09-20 16:54:28 +0000
committerJim Blandy <jimb@codesourcery.com>2004-09-20 16:54:28 +0000
commitd73f140ac2cd081eb1bd6a0c33d215632e9bcce7 (patch)
tree20ca154b48d5737d1f4430db11cc98932130daef /gdb/minsyms.c
parentadbef1f0144e953ef9b546bf944040537aef6741 (diff)
downloadgdb-d73f140ac2cd081eb1bd6a0c33d215632e9bcce7.zip
gdb-d73f140ac2cd081eb1bd6a0c33d215632e9bcce7.tar.gz
gdb-d73f140ac2cd081eb1bd6a0c33d215632e9bcce7.tar.bz2
* minsyms.c (lookup_minimal_symbol): Doc fix.
Diffstat (limited to 'gdb/minsyms.c')
-rw-r--r--gdb/minsyms.c10
1 files changed, 9 insertions, 1 deletions
diff --git a/gdb/minsyms.c b/gdb/minsyms.c
index 3aeda7d..635d0cc 100644
--- a/gdb/minsyms.c
+++ b/gdb/minsyms.c
@@ -145,7 +145,15 @@ add_minsym_to_demangled_hash_table (struct minimal_symbol *sym,
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). */
+ 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,