From: Yoshinori Toshima <yoshinori.toshima@oracle.com>
To: gdb-patches@sourceware.org
Subject: Please add code to pick up SOLIB_SEARCH_PATH env var.
Date: Thu, 16 Dec 2010 09:29:00 -0000 [thread overview]
Message-ID: <4D09DB33.902@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
Hello,
I have a small enhancement request for GDB to make it easier to
use when debugging core file from other systems which have
different libraries.
Description:
When debugging a core file from released product, it is convenient
to have gdb use shared libraries in a directory which contains the
libraries and executable taken from the system which caused the
crash. It is possible to perform this by gdb command "set
solib-search-path <path>". This means some commands are required
after starting gdb. If we can set solib-search-path at gdb startup,
it is easier to use. This is useful when we use GDB programmatically.
HP-UX port of GDB has this feature via env var GDB_SHLIB_PATH.
GDB does not have the feature yet, though it mentions SOLIB_SEARCH_PATH
in solib.c.
I changed solib.c to pick up SOLIB_SEARCH_PATH at startup and set
it to solib_search_path in solib.c initialization. It worked as
expected.
Attached solib-patch.diff is based on solib.c in gdb 7.2.
ChangeLog entry:
2010-12-16 Yoshinori Toshima <yoshinori.toshima@oracle.com>
* solib.c: Pick up SOLIB_SEARCH_PATH env var to set solib-search-path at
startup.
Regards,
Yoshinori Toshima
[-- Attachment #2: solib-patch.diff --]
[-- Type: text/plain, Size: 1172 bytes --]
*** gdb.org/solib.c 2010-12-16 17:51:11.000000000 +0900
--- gdb/solib.c 2010-12-16 17:55:29.000000000 +0900
*************** solib_global_lookup (const struct objfil
*** 1448,1453 ****
--- 1448,1469 ----
return NULL;
}
+ void
+ check_solib_search_path_env ()
+ {
+ char *envvar = getenv("SOLIB_SEARCH_PATH");
+ if (envvar != NULL) {
+ if (access(envvar, R_OK) == 0) {
+ solib_search_path = envvar;
+ fprintf_filtered (gdb_stdout, _("Picked up SOLIB_SEARCH_PATH %s.\n"),
+ envvar);
+ } else {
+ warning (_("SOLIB_SEARCH_PATH %s is not accessible. "
+ "Ignored."), envvar);
+ }
+ }
+ }
+
extern initialize_file_ftype _initialize_solib; /* -Wmissing-prototypes */
*************** For other (relative) files, you can add
*** 1491,1496 ****
--- 1507,1514 ----
add_alias_cmd ("solib-absolute-prefix", "sysroot", class_support, 0,
&showlist);
+ check_solib_search_path_env();
+
add_setshow_optional_filename_cmd ("solib-search-path", class_support,
&solib_search_path, _("\
Set the search path for loading non-absolute shared library symbol files."), _("\
next reply other threads:[~2010-12-16 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 9:29 Yoshinori Toshima [this message]
2010-12-16 10:26 ` Pierre Muller
2010-12-16 13:23 ` Yoshinori Toshima
2010-12-16 14:23 ` Yoshinori Toshima
2010-12-16 13:07 ` Pedro Alves
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=4D09DB33.902@oracle.com \
--to=yoshinori.toshima@oracle.com \
--cc=gdb-patches@sourceware.org \
/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