On Thu, Oct 16, 2008 at 3:39 PM, John Levon <levon@movementarian.org> wrote:
> > >        96193 47.5567 vmlinux
> > >        60204 29.7642 receiver
> > >        20059  9.9169 libc-2.5.so
> > >        11306  5.5896 libACE-5.6.5.so
> > >         8286  4.0965 anon (tgid:1093 range:0xffffe000-0xfffff000)
> >
> > That looks awfully like the vsyscall region. Look at /proc/1093/maps
> The row matching this range looks as follows:
> ffffe000-fffff000 r-xp ffffe000 00:00 0
> As expected, it is not backed by a file. I'm not sure how I can interpret
> this. Can you help me?

What kernel version are you running? the maps file normally identifies
vsyscall, you really don't have "[vdso]" at the end?

No, the column showing the mapped binary is empty. No [vdso] anywhere in /proc/1093/maps

Anyway, that's what it is, google for its meaning.

So are you saying it is always vsyscall, even if it is not explicitly mentioned?
> Both files contain "bad_gs" but not at the same address. Also the total
> number of symbols ist not the same. I guess this confirms your assumption
> that I'm using the wrong vmlinux. However I'm not sure how to find the right
> one. I am on Red Hat and therefore had to download the rpm with the vmlinux.

What rpm? Just make sure you get the debuginfo version of your kernel
RPM and it's definitely what you're running

Stupid me. I rechecked the packages and discovered that I installed kernel-debug-debuginfo instead of kernel-debuginfo. This is working now, thanks for the hint!