diff options
author | Fred Fish <fnf@specifix.com> | 2001-10-30 04:05:36 +0000 |
---|---|---|
committer | Fred Fish <fnf@specifix.com> | 2001-10-30 04:05:36 +0000 |
commit | b7209cb4ed7852044e3ec55daec11e9f693e401c (patch) | |
tree | 547f5a9fd0b47af1195b939f6df8064a8036065b /gdb/symfile.h | |
parent | 310a798eb8257ba2f40cf0aaa934ad3676108b16 (diff) | |
download | gdb-b7209cb4ed7852044e3ec55daec11e9f693e401c.zip gdb-b7209cb4ed7852044e3ec55daec11e9f693e401c.tar.gz gdb-b7209cb4ed7852044e3ec55daec11e9f693e401c.tar.bz2 |
Changes approved by kev@cygnus.com, ezannoni@cygnus.com, eliz@is.elta.co.il.
Changelog:
2001-10-27 Fred Fish <fnf@redhat.com>
* symfile.c (auto_solib_add): Update comment to note that
this variable is now just used as a boolean to control shlib
autoloading, and clarify when it is used.
* symfile.h (auto_solib_add): Ditto.
* symfile.c (auto_solib_limit): New variable that holds the
autoloading threshold instead of overloading auto_solib_add.
* symfile.h (auto_solib_limit): Ditto.
* irix5-nat.c (_initialize_solib): Change auto-solib-add
variable from var_zinteger to var_boolean and update help.
* osfsolib.c (_initialize_solib): Ditto.
* pa64solib.c (_initialize_pa64_solib): Ditto.
* solib.c (_initialize_solib): Ditto.
* somsolib.c (_initialize_som_solib): Ditto.
* xcoffsolib.c (_initialize_solib): Ditto.
* pa64solib.c (pa64_solib_total_st_size): Update comment to
note that the new auto_solib_limit variable is used instead
of overloading auto_solib_add variable.
(_initialize_pa64_solib): Ditto.
* somsolib.c (som_solib_total_st_size): Ditto.
(_initialize_som_solib): Ditto.
* pa64solib.c (_initialize_pa64_solib): Add new set/show
commands for auto-solib-limit variable.
* somsolib.c (_initialize_som_solib): Ditto
* pa64solib.c (add_to_solist): Check that auto_solib_add is
set and use auto_solib_limit as the threshold size instead
of auto_solib_add.
* somsolib.c (som_solib_add): Ditto, and also change warning
text about size threshold exceeded.
doc/ChangeLog:
2001-10-28 Fred Fish <fnf@redhat.com>
* gdb.texinfo (auto-solib-add): Change docs to match
implementation change.
(auto-solib-limit): Add docs for new variable.
Diffstat (limited to 'gdb/symfile.h')
-rw-r--r-- | gdb/symfile.h | 27 |
1 files changed, 18 insertions, 9 deletions
diff --git a/gdb/symfile.h b/gdb/symfile.h index 36447d7..a6bf3f6 100644 --- a/gdb/symfile.h +++ b/gdb/symfile.h @@ -218,18 +218,27 @@ extern char *obconcat (struct obstack *obstackp, const char *, const char *, /* Variables */ -/* whether to auto load solibs at startup time: 0/1. +/* If non-zero, shared library symbols will be added automatically + when the inferior is created, new libraries are loaded, or when + attaching to the inferior. This is almost always what users will + want to have happen; but for very large programs, the startup time + will be excessive, and so if this is a problem, the user can clear + this flag and then add the shared library symbols as needed. Note + that there is a potential for confusion, since if the shared + library symbols are not loaded, commands like "info fun" will *not* + report all the functions that are actually present. */ - On all platforms, 0 means "don't auto load". - - On HP-UX, > 0 means a threshhold, in megabytes, of symbol table which will - be auto loaded. When the cumulative size of solib symbol table exceeds - this threshhold, solibs' symbol tables will not be loaded. +extern int auto_solib_add; - On other platforms, > 0 means, "always auto load". - */ +/* For systems that support it, a threshold size in megabytes. If + automatically adding a new library's symbol table to those already + known to the debugger would cause the total shared library symbol + size to exceed this threshhold, then the shlib's symbols are not + added. The threshold is ignored if the user explicitly asks for a + shlib to be added, such as when using the "sharedlibrary" + command. */ -extern int auto_solib_add; +extern int auto_solib_limit; /* From symfile.c */ |