From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Ulrich Weigand <uweigand@de.ibm.com>, jan.kratochvil@redhat.com
Subject: [PATCH v2] Skip vDSO when reading SO list (PR 8882)
Date: Tue, 24 Sep 2013 17:47:00 -0000 [thread overview]
Message-ID: <87eh8ep0wy.fsf@br87z6lw.de.ibm.com> (raw)
Suppress the warning when the vDSO's pathname from the SO list in a core
file can not be accessed. The glibc's dynamic loader uses empty-string
literals for both the executable as well as the vDSO, and the compiler
collates both of them to a single string literal. Thus the vDSO's
l_name address matches the main executable's. This property is used as
a criteria for identifying and silently skipping the vDSO.
This version includes a small test case and follows Jan's proposal of
moving the suppression logic after the pathname read has already failed.
OK to apply?
ChangeLog:
2013-09-24 Andreas Arnez <arnez@linux.vnet.ibm.com>
* solib-svr4.c (svr4_read_so_list): Skip the vDSO when reading
link map entries.
testsuite/ChangeLog:
2013-09-24 Andreas Arnez <arnez@linux.vnet.ibm.com>
* gdb.base/corefile.exp: Add a check to assure warning-free
core-file load.
Index: gdb/gdb/solib-svr4.c
===================================================================
--- gdb.orig/gdb/solib-svr4.c
+++ gdb/gdb/solib-svr4.c
@@ -1310,6 +1310,7 @@ static int
svr4_read_so_list (CORE_ADDR lm, CORE_ADDR prev_lm,
struct so_list ***link_ptr_ptr, int ignore_first)
{
+ struct so_list *first = NULL;
CORE_ADDR next_lm;
for (; lm != 0; prev_lm = lm, lm = next_lm)
@@ -1349,6 +1350,7 @@ svr4_read_so_list (CORE_ADDR lm, CORE_AD
{
struct svr4_info *info = get_svr4_info ();
+ first = new;
info->main_lm_addr = new->lm_info->lm_addr;
do_cleanups (old_chain);
continue;
@@ -1359,8 +1361,16 @@ svr4_read_so_list (CORE_ADDR lm, CORE_AD
SO_NAME_MAX_PATH_SIZE - 1, &errcode);
if (errcode != 0)
{
- warning (_("Can't read pathname for load map: %s."),
- safe_strerror (errcode));
+ /* If this entry's l_name address matches that of the
+ inferior executable, then this is not a normal shared
+ object, but (most likely) a vDSO. In this case, silently
+ skip it; otherwise emit a warning. */
+ if (! (first != NULL
+ && new->lm_info->l_name == first->lm_info->l_name))
+ {
+ warning (_("Can't read pathname for load map: %s."),
+ safe_strerror (errcode));
+ }
do_cleanups (old_chain);
continue;
}
Index: gdb/gdb/testsuite/gdb.base/corefile.exp
===================================================================
--- gdb.orig/gdb/testsuite/gdb.base/corefile.exp
+++ gdb/gdb/testsuite/gdb.base/corefile.exp
@@ -255,3 +255,19 @@ if ![is_remote target] {
gdb_exit
}
+
+# Test warning-free core file load. E.g., a Linux vDSO used to
+# trigger this warning:
+# warning: Can't read pathname for load map: Input/output error.
+
+clean_restart ${testfile}
+
+set test "core-file warning-free"
+gdb_test_multiple "core-file $corefile" $test {
+ -re "warning: .*\r\n.*\r\n$gdb_prompt $" {
+ fail $test
+ }
+ -re "\r\n$gdb_prompt $" {
+ pass $test
+ }
+}
next reply other threads:[~2013-09-24 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 17:47 Andreas Arnez [this message]
2013-09-24 18:08 ` Jan Kratochvil
2013-09-25 8:55 ` Andreas Arnez
2013-09-25 11:53 ` Ulrich Weigand
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=87eh8ep0wy.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=uweigand@de.ibm.com \
/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