Open ghost opened 10 years ago
Can you type "bt" or "backtrace" at the "gdb" prompt to rewind the stack to see the function call leading up to the crash ?
If your Virtuoso binary is not stripped ie symbols removed (" file virtuoso-t ") you may need to rebuild without stripping as follows:
Here the bt result :
(gdb) bt
#0 0x00000000006785be in ?? ()
#1 0x0000000000657c7e in ?? ()
#2 0x00000000006183b9 in ?? ()
#3 0x000000000061f053 in table_source_input ()
#4 0x000000000061872a in ?? ()
#5 0x00000000006189f1 in ?? ()
#6 0x000000000061f38f in table_source_input ()
#7 0x00000000005e8162 in ?? ()
#8 0x0000000000654600 in aq_qr_func ()
#9 0x0000000000462e7d in aq_thread_func ()
#10 0x0000000000930d2f in ?? ()
#11 0x00007f7da3d889ca in start_thread () from /lib/libpthread.so.0
#12 0x00007f7da365e21d in clone () from /lib/libc.so.6
#13 0x0000000000000000 in ?? ()
(gdb) frame 0x00000000006785be
#0 0x0000000000000000 in ?? ()
(gdb) info locals
No symbol table info available.
We have a big dump of around 47Gb and 1.3Gb compressed. I can provide it too.
The binary is stripped and thus needs to be rebuilt with the symbols in place to the the missing symbol info in the back trace ...
Ok, but the thing is I don't know how to reproduce the segfault to remake the call trace. Is-it a problem ?
If it is not instantly reproducible then just leave it running with the debug binary and next time it does crash the resultant core will have the back trace with symbol info.
Ok I do that !
Hi,
My Virtuoso crashed with a segfault and I don't know why. Here all the message and analyse that I can provide on the error. Syslog message :
And GDB analyse :
Virtuoso version :
Hope these Informations will be usefull.
Best.
Julien.