Anybody know how to debug things like this?
Eric S. Raymond
esr at thyrsus.com
Thu Jul 14 22:39:04 UTC 2016
Hal Murray <hmurray at megapathdsl.net>:
> I'm working on segcomp. I'm at the stage where things mostly work and I'm
> trying to find obscure code paths that use a syscall that isn't yet on the OK
> The SIGSYS means it tried to call something that wasn't on the list.
> Normally, a simple backtrace will let me can figure out what it is and add
> the appropriate call to the list.
> It might be in the magic part of creating a new thread, but that has been
> working for months.
> Program received signal SIGSYS, Bad system call.
> 0x41d810d8 in clone () from /lib/libc.so.6
> Missing separate debuginfos, use: debuginfo-install glibc-2.16-34.fc18.i686
> libattr-2.4.46-7.fc18.i686 libcap-2.22-5.fc18.i686 libgcc-4.7.2-8.fc18.i686
> (gdb) bt
> #0 0x41d810d8 in clone () from /lib/libc.so.6
> #1 0x00000001 in ?? ()
> #2 0xb7fcbb40 in ?? ()
> #3 0x00000000 in ?? ()
> (gdb) info threads
> Id Target Id Frame
> * 1 Thread 0xb7fcc6c0 (LWP 18519) "ntpd" 0x41d810d8 in clone ()
> from /lib/libc.so.6
Sorry, I've never dealt with this.
Seems like a situation made for investigating with Mozilla rr.
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
More information about the devel