|
Thanks for the gdb suggestion. I'm not very fluent in native development, but I was able to get this (center of the trace where it is bouncing around inside libpython elided):
Thread 1 "calibre" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x00007ffff7be1864 in __GI_abort () at abort.c:79
#2 0x00007fffe821b452 in ?? () from /usr/lib/x86_64-linux-gnu/libffi.so.8
#3 0x00007fffd6179594 in ?? ()
from /opt/calibre/lib/python2.7/lib-dynload/_ctypes.so
#4 0x00007ffff783769b in ?? ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#5 0x00007fffd61753d7 in ?? ()
from /opt/calibre/lib/python2.7/lib-dynload/_ctypes.so
#6 0x00007ffff78592b2 in ?? ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#7 0x00007ffff78acaee in PyEval_EvalFrameEx ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#8 0x00007ffff78ab525 in PyEval_EvalFrameEx ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#9 0x00007ffff78aefbc in PyEval_EvalCodeEx ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#10 0x00007ffff78af0d9 in PyEval_EvalCode ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#11 0x00007ffff78c2ddc in PyImport_ExecCodeModuleEx ()
...
#54 0x00007ffff78a5087 in PyEval_CallObjectWithKeywords ()
from /opt/calibre/lib/../lib/libpython2.7.so.1.0
#55 0x00007ffff7dbe529 in execute_python_entrypoint ()
from /opt/calibre/lib/libcalibre-launcher.so
#56 0x0000000000400636 in ?? ()
#57 0x00007ffff7be3cb2 in __libc_start_main (main=0x400600, argc=1,
argv=0x7fffffffe5c8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffe5b8)
at ../csu/libc-start.c:314
#58 0x0000000000400669 in ?? ()
So python calling out to something native?
|