This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: staprun segmentation fault with module `fglrx' in use
Hi -
On Sun, Mar 18, 2007 at 03:53:47PM +0000, Guanqun Lu wrote:
> Here's the output from my console:
> [...]
> enter send_module() module_name is fglrx
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1210034512 (LWP 5919)]
> 0xb7e6f29b in strlen () from /lib/libc.so.6
> (gdb) backtrace
> #0 0xb7e6f29b in strlen () from /lib/libc.so.6
> #1 0xb7e445ac in vfprintf () from /lib/libc.so.6
> #2 0xb7e623f1 in vsnprintf () from /lib/libc.so.6
> #3 0xb7e49845 in snprintf () from /lib/libc.so.6
> #4 0x0804a834 in send_module (mname=0x2e742e65 <Address 0x2e742e65 out of
> bounds>) at runtime/staprun/symbols.c:56
> #5 0x636e6f6b in ?? ()
> [...]
> Hope this helps.
Yes. OK, a few more ideas (since this is not crashing on my
nvidia-blob-laden workstation):
There are only two snprintf calls in symbols.c, and neither looks on
its face wrong. What does "ls -alR /sys/module/flgrx" show? It would
be nice to see the parameter list to snprintf(), or a look at each
dirent structure coming back from readdir(). Do you have systemtap's
own debugging information available to gdb, or does gentoo strip it
away for good?
- FChE