From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: vijay nag <vijunag@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: vdso
Date: Wed, 03 Jul 2013 08:42:00 -0000 [thread overview]
Message-ID: <20130703084207.GA598@host2.jankratochvil.net> (raw)
In-Reply-To: <CAKhyrx_TULNrWwSJ0zPq4tgd8MOpkhSRYZfbMRFcRLw7P0mj4Q@mail.gmail.com>
On Wed, 03 Jul 2013 10:34:43 +0200, vijay nag wrote:
> cat /proc/15896/smaps | grep vdso
> 778:b7fff000-b8000000 r-xp b7fff000 00:00 0 [vdso]
>
> Does vdso come with symbols ?
For basic ELF symbols it does. Try:
dump memory /tmp/vdso.so 0xb7fff000 0xb8000000
readelf -Ws /tmp/vdso.so
and .dynsym section there should contain the symbols:
4: ffffffffff700ba0 404 FUNC GLOBAL DEFAULT 15 __vdso_gettimeofday@@LINUX_2.6
5: ffffffffff700d60 61 FUNC GLOBAL DEFAULT 15 __vdso_getcpu@@LINUX_2.6
etc.
Then there are also DWARF symbols to see even filenames / line numbers but
those .debug_* sections at least Fedora ships only on disk in kernel-debuginfo
rpm. The symbols get loaded automatically by GDB:
lrwxrwxrwx 1 root root 61 Jul 2 00:43 /usr/lib/debug/.build-id/92/0bba09195bde2b45a7a4eaec1dc78c3157c0f5 -> ../../../../../lib/modules/3.9.8-200.fc18.x86_64/vdso/vdso.so*
lrwxrwxrwx 1 root root 58 Jul 2 00:43 /usr/lib/debug/.build-id/92/0bba09195bde2b45a7a4eaec1dc78c3157c0f5.debug -> ../../lib/modules/3.9.8-200.fc18.x86_64/vdso/vdso.so.debug
-rwxr-xr-x 1 root root 4856 Jun 28 16:56 /lib/modules/3.9.8-200.fc18.x86_64/vdso/vdso.so*
-r--r--r-- 1 root root 104848 Jun 28 16:56 /usr/lib/debug/lib/modules/3.9.8-200.fc18.x86_64/vdso/vdso.so.debug
$ rpm -qf /lib/modules/3.9.8-200.fc18.x86_64/vdso/vdso.so /usr/lib/debug/lib/modules/3.9.8-200.fc18.x86_64/vdso/vdso.so.debug
kernel-3.9.8-200.fc18.x86_64
kernel-debuginfo-3.9.8-200.fc18.x86_64
You should check first /tmp/vdso.so to see whether your Linux kernel or GDB is
the problem.
Jan
next prev parent reply other threads:[~2013-07-03 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 8:34 vdso vijay nag
2013-07-03 8:42 ` Jan Kratochvil [this message]
2013-07-03 9:15 ` vdso vijay nag
2013-07-03 9:03 ` vdso Jan Kratochvil
2013-07-03 9:06 ` vdso vijay nag
[not found] ` <CAKhyrx_9fSc5wMaXaX76bFOPJbuVFttDNJ-YDa28wz5obJHQyQ@mail.gmail.com>
2013-07-03 14:49 ` vdso Jan Kratochvil
[not found] ` <20130703144857.GA27367@host2.jankratochvil.net>
[not found] ` <CAKhyrx8GCE7bYeZe9gnNT_aZN74oM--kd_oZr1+cjqt67oOzVQ@mail.gmail.com>
[not found] ` <20130704061052.GA19661@host2.jankratochvil.net>
[not found] ` <CAKhyrx8pAR9aKC1=-_HnwJ=ssb4B7LGUYM6CRqxY68xx+duprA@mail.gmail.com>
2013-07-05 6:12 ` Fwd: vdso vijay nag
[not found] ` <20130705184238.GA661@host2.jankratochvil.net>
2013-07-08 6:50 ` vijay nag
2013-07-08 8:47 ` Jan Kratochvil
2013-07-08 9:12 ` vijay nag
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=20130703084207.GA598@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=vijunag@gmail.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