From f056b22b92a0e95582f47591e0c327c642dfd80f Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Tue, 11 Feb 2020 18:11:32 -0700 Subject: [PATCH] Update a comment in psymtab.h This updates a comment in psymtab.h to reflect the current reality. gdb/ChangeLog 2020-02-11 Tom Tromey * psymtab.h: Update comment. Change-Id: I438bb5929c3ebd1a4c6e9a902490f2ef63014ab3 --- gdb/ChangeLog | 4 ++++ gdb/psymtab.h | 4 +++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 4a4fa054c89..43fe4de6857 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2020-02-11 Tom Tromey + + * psymtab.h: Update comment. + 2020-02-11 Tom Tromey * gdb_obstack.h (struct auto_obstack): Use diff --git a/gdb/psymtab.h b/gdb/psymtab.h index d66547418cb..040b973927c 100644 --- a/gdb/psymtab.h +++ b/gdb/psymtab.h @@ -36,7 +36,9 @@ struct partial_symbol; other memory managed by this class), or on the per-BFD object. The only link from the psymtab storage object back to the objfile (or objfile_obstack) that is made by the core psymtab code is the - compunit_symtab member in the psymtab. + compunit_symtab member in the standard_psymtab -- and a given + symbol reader can avoid this by implementing its own subclasses of + partial_symtab. However, it is up to each symbol reader to maintain this invariant in other ways, if it wants to reuse psymtabs across multiple -- 2.30.2