Version: 1.0.21-9
According to
http://stackoverflow.com/questions/2702628/gdb-cannot-find-new-threads-generic-error,
the gdb problems are caused by scanimage's use of libpthreads.so.0 via
dlopen. Workaround that gives a much better backtrace:
$ SANE_DEBUG_DLL=3 LD_PRELOAD=/lib/libpthread.so.0
Sam Morris s...@robots.org.uk wrote:
Hi Sam,
[dll] sane_exit: calling backend `net's exit function
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeca0a700 (LWP 18984)]
0x7fffeca2fe91 in ?? () from /usr/lib/libdbus-1.so.3
(gdb) where
#0
On Fri, Mar 25, 2011 at 05:43:06PM +0100, Julien BLACHE wrote:
Sam Morris s...@robots.org.uk wrote:
Hi Sam,
[dll] sane_exit: calling backend `net's exit function
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeca0a700 (LWP 18984)]
0x7fffeca2fe91
Sam Morris s...@robots.org.uk wrote:
Hi Sam,
I ran a few more tests and the backtrace alternated between the one you
quoted above, and one that crashed in hpaio's exit function. Disabling
Aha, interesting, exactly what I suspected. It may have to do with
having several DBus connections in the
4 matches
Mail list logo
