Re: issue with libthr?

On Sat, Jun 01, 2013 at 12:54:14AM -0700, Waitman Gobble wrote:
> 
> Hi,
> 
> I'm getting a ton of core dumps from Python and any software that uses Python,
> ie has USE_PYTHON_BUILD=yes in Makefile.
> 
> hundreds of msgs in dmesg:
> pid 36637 (seamonkey), uid 1001: exited on signal 11 (core dumped)
> pid 36986 (seamonkey), uid 1001: exited on signal 11 (core dumped)
> pid 37054 (seamonkey), uid 1001: exited on signal 11 (core dumped)
> pid 51780 (seamonkey), uid 1001: exited on signal 11 (core dumped)
> pid 83350 (python2.7), uid 0: exited on signal 6 (core dumped)
> 
> from gdb it seems to me to be libthr related? I've noticed a couple updates in
> May.. wonder if it's related? I've only noticed this issue in the past week,
> after a complete rebuild and updated.
> 
> > uname -a
> FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r251111: Wed May
> 29 16:44:31 PDT 2013     root_at_dx.burplex.com:/usr/obj/usr/src/sys/FURAHA 
> amd64
> 
> gdb:
> 
> seamonkey
> 
> (gdb) bt
> #0  0x00000008011ee8ca in thr_kill () from /lib/libc.so.7
> #1  0x000000080316b585 in XRE_InstallX11ErrorHandler ()
>    from /usr/local/lib/seamonkey/libxul.so
> #2  0x0000000800f73286 in swapcontext () from /lib/libthr.so.3
> #3  0x0000000800f72e89 in sigaction () from /lib/libthr.so.3
> #4  0x00007ffffffff1d3 in ?? ()
> #5  0x0000000800f72d70 in sigaction () from /lib/libthr.so.3
> Previous frame inner to this frame (corrupt stack?)
> 
> 
> python
> 
> (gdb) bt
> #0  0x000000080100d8ca in thr_kill () from /lib/libc.so.7
> #1  0x00000008010d2e9c in abort () from /lib/libc.so.7
> #2  0x0000000803e4f05b in free ()
>    from /usr/local/lib/python2.7/lib-dynload/_ctypes.so
> #3  0x0000000800d9319f in pthread_mutex_destroy () from /lib/libthr.so.3
> #4  0x00000008010269ff in closedir () from /lib/libc.so.7
> #5  0x00000000004b545c in initposix ()
> #6  0x000000000047fb75 in PyEval_EvalFrameEx ()
> #7  0x000000000047d824 in PyEval_EvalCodeEx ()
> #8  0x0000000000484256 in _PyEval_SliceIndex ()
> #9  0x00000000004810cd in PyEval_EvalFrameEx ()
> #10 0x000000000047d824 in PyEval_EvalCodeEx ()
> #11 0x00000000004d5f56 in PyFunction_SetClosure ()
> #12 0x000000000041ffeb in PyObject_Call ()
> #13 0x0000000000482085 in PyEval_EvalFrameEx ()
> #14 0x000000000047d824 in PyEval_EvalCodeEx ()
> #15 0x0000000000484256 in _PyEval_SliceIndex ()
> #16 0x00000000004810cd in PyEval_EvalFrameEx ()
> #17 0x000000000047d824 in PyEval_EvalCodeEx ()
> #18 0x0000000000484256 in _PyEval_SliceIndex ()
> #19 0x00000000004810cd in PyEval_EvalFrameEx ()
> #20 0x000000000047d824 in PyEval_EvalCodeEx ()
> #21 0x0000000000484256 in _PyEval_SliceIndex ()
> #22 0x00000000004810cd in PyEval_EvalFrameEx ()
> #23 0x00000000004841f2 in _PyEval_SliceIndex ()
> #24 0x00000000004810cd in PyEval_EvalFrameEx ()
> #25 0x00000000004841f2 in _PyEval_SliceIndex ()
> #26 0x00000000004810cd in PyEval_EvalFrameEx ()
> #27 0x00000000004841f2 in _PyEval_SliceIndex ()
> #28 0x00000000004810cd in PyEval_EvalFrameEx ()
> #29 0x00000000004841f2 in _PyEval_SliceIndex ()
> #30 0x00000000004810cd in PyEval_EvalFrameEx ()
> #31 0x00000000004841f2 in _PyEval_SliceIndex ()
> #32 0x00000000004810cd in PyEval_EvalFrameEx ()
> #33 0x000000000047d824 in PyEval_EvalCodeEx ()
> #34 0x000000000047d156 in PyEval_EvalCode ()
> #35 0x00000000004a1361 in PyRun_FileExFlags ()
> #36 0x00000000004a0eb1 in PyRun_SimpleFileExFlags ()
> #37 0x0000000000417549 in Py_Main ()
> #38 0x000000000041692f in main ()
> 
> 
> Any help/pointers much appreciated.

You cannot even guess what is going on without a proper debug information.
Recompile and reinstall the libc/libthr/rtld with the debugging symbols
to get proper backtraces.

Anyway, two backtraces you demostrated, although not giving much useful
data, look very different.  More, the second backtrace suggests that
there is either a bug in python interposing of malloc or memory corruption.