public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13097] New: gdb regression: Excessive linux-vdso.so.1 name Date: Tue, 16 Aug 2011 12:36:00 -0000 [thread overview] Message-ID: <bug-13097-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13097 Bug #: 13097 Summary: gdb regression: Excessive linux-vdso.so.1 name Product: glibc Version: 2.14 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: jan.kratochvil@redhat.com Classification: Unclassified Description of problem: GDB has started to print on each `run': warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? Version-Release number of selected component (if applicable): FAIL: glibc-2.14.90-5.x86_64 PASS: glibc-2.14.90-4.x86_64 Guessing it is due to: commit 73d7af4f4c2b394063cb0b3a33ee2b00b5ad80b4 Implement LD_DEBUG=scopes How reproducible: Always. Steps to Reproduce: echo 'main(){}'|gcc -x c -;../gdb -nx ./a.out -ex start -ex 'info shared' -ex c -ex q Actual results: Starting program: .../a.out warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? Temporary breakpoint 1, 0x0000000000400478 in main () >From To Syms Read Shared Object Library 0x00007ffff7ddbb20 0x00007ffff7df513a Yes /lib64/ld-linux-x86-64.so.2 No linux-vdso.so.1 0x00007ffff7a4adc0 0x00007ffff7b80050 Yes /lib64/libc.so.6 Continuing. Expected results: Starting program: .../a.out Temporary breakpoint 1, 0x0000000000400478 in main () >From To Syms Read Shared Object Library 0x00007ffff7ddbb20 0x00007ffff7df4eda Yes /lib64/ld-linux-x86-64.so.2 0x00007ffff7a4ad30 0x00007ffff7b7ff60 Yes /lib64/libc.so.6 Continuing. Additional info: glibc vdso had its name in the link map "" before. I do not see why the name should be different when there is no corresponding on-disk file for it. Should GDB ignore for symbol resolution libraries with literal path-less name "linux-vdso.so.1"? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-08-16 12:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-16 12:36 jan.kratochvil at redhat dot com [this message] 2011-09-06 1:39 ` [Bug libc/13097] " drepper.fsp at gmail dot com 2012-08-14 12:54 ` jan.kratochvil at redhat dot com 2012-11-24 19:10 ` jan.kratochvil at redhat dot com 2012-11-24 21:40 ` ldv at altlinux dot org 2013-05-27 21:10 ` naesten at gmail dot com 2013-05-28 20:02 ` carlos at redhat dot com 2013-06-09 3:26 ` naesten at gmail dot com 2014-02-07 2:57 ` [Bug dynamic-link/13097] " jsm28 at gcc dot gnu.org 2014-02-16 17:50 ` jackie.rosen at hushmail dot com 2014-02-20 7:21 ` kalvdans at gmail dot com 2014-03-24 1:24 ` ovidiu.b13 at gmail dot com 2014-05-28 19:41 ` schwab at sourceware dot org 2014-06-27 12:25 ` fweimer at redhat dot com
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=bug-13097-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).