[Bug libc/13097] New: gdb regression: Excessive linux-vdso.so.1 name

["jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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.