This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: registration error (rc -84)


Daniel Doron <danielmeirdoron@gmail.com> writes:

> I run stap-report and the only thing that seems out of place to me is
> the Build ID diff between the kernel and debug-kernel.
>
> == (eu-readelf -n /boot/vmlinuz-3.10.0-514.26.2.el7.x86_64 || readelf
> -n /boot/vmlinuz-3.10.0-514.26.2.el7.x86_64) | grep Build ==
>     Build ID: 62b54b1aac6eeaa4cd469439011f8a97558400e0
> == (eu-readelf -n
> /usr/lib/debug/lib/modules/3.10.0-514.26.2.el7.x86_64/vmlinux ||
> readelf -n /usr/lib/debug/lib/modules/3.10.0-514.26.2.el7.x86_64/vmlinux)
> | grep Build ==
>     Build ID: 9812ec6054800f5f9ee0e65ad9c780c8273200c3

I recall seeing something like this when someone used a funky community
rhel7 respin that reused the exact rhel7 n-v-r, and tried to use someone
else's debuginfo.

Nevertheless, stap does verify buildid matches at startup in many cases.
I'm very curious why that wouldn't have worked.  Would you mind
rerunning your job with this extra option:

# stap -DDEBUG_SYMBOLS=1 ...other options...


- FChE


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]