At Wed, 28 Dec 2005 08:01:35 +0100,
Michael Sperber wrote:
> > Strangly when running scsh in gdb the problem disappears.
>
> But you should be able to force a core file and look at the backtrace,
> right?
>
I got the trace by attaching to the process with gdb:
#0 0x41527124 in __pthread_sigsuspend () from /lib/libpthread.so.0
#1 0x41525f29 in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0
#2 0x41526c89 in pthread_create@@GLIBC_2.1 () from /lib/libpthread.so.0
#3 0x414f207c in sqlite3OsTempFileName () from /usr/lib/libsqlite3.so.0
#4 0x414f240d in sqlite3OsOpenReadWrite () from /usr/lib/libsqlite3.so.0
#5 0x414f3a6d in sqlite3pager_open () from /usr/lib/libsqlite3.so.0
#6 0x414da70a in sqlite3BtreeOpen () from /usr/lib/libsqlite3.so.0
#7 0x414f0591 in sqlite3BtreeFactory () from /usr/lib/libsqlite3.so.0
#8 0x414f0ad7 in sqlite3_create_collation () from /usr/lib/libsqlite3.so.0
#9 0x414cc29f in s48_sqlite3_open () from /usr/lib/scsh-sqlite3.so
#10 0x0805ead2 in s48_external_call ()
#11 0x08059d1a in s48_restart ()
#12 0x0805b9ed in s48_call_startup_procedure ()
#13 0x0804edea in internal_s48_main ()
#14 0x0804ea45 in main ()
Kristof Bastiaensen
|