summaryrefslogtreecommitdiff
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
commit26bdd478fa0a2012bc597b9bfbce64e8cec0ac94 (patch)
tree1f45c121b7af59c773223176cf881abe3ae04bea /gdb/minsyms.c
parentcff8a14ba9c41eeaf0b8bb9e29325a5560d15cb4 (diff)
downloadgdb-26bdd478fa0a2012bc597b9bfbce64e8cec0ac94.tar.gz
* 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 3aeda7d0815..635d0cc4a17 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,