Subject Re: [firebird-support] How to detect the source of a "firebird terminated abnormally (-1)" error?
Author Gabor Boros
2018. 05. 31. 21:02 keltezéssel, Gabor Boros mlnglsts@...
[firebird-support] írta:
> Hi All,
> I found some "firebird terminated abnormally (-1)" errors in
> firebird.log on my development machine. How can I detect it's source?
> My tip is a self made UDF (no input parameter, one TIMESTAMP output and
> written with Free Pascal). Can I stress test the UDF/problem somehow? (I
> know the problem only from the log and use 3.0.3 SuperServer and Linux
> 64bit.)

Switched on BugcheckAbort and later found a core file in /tmp. See the
gdb output below. Any idea?

Reading symbols from /opt/firebird/bin/.debug/firebird.debug...done.

warning: core file may not match specified executable file.
[New LWP 2222]
[New LWP 2092]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/".
Core was generated by `/opt/firebird/bin/firebird'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fc5f2eef880 in ?? ()

(gdb) thread apply all bt

Thread 2 (Thread 0x7fc5fbcba7c0 (LWP 2092)):
#0 0x00007fc5fa46db9d in nanosleep () from
#1 0x0000000000453a01 in Thread::sleep
(milliseconds=milliseconds@entry=100) at
#2 0x000000000042fabb in Worker::shutdown () at
#3 0x00000000004365ed in SRVR_multi_thread (main_port=0x7fc5fbc8d6c0,
flags=flags@entry=2) at
#4 0x0000000000445fba in main (argc=<optimized out>, argv=<optimized
out>) at

Thread 1 (Thread 0x7fc5f3a2c700 (LWP 2222)):
#0 0x00007fc5f2eef880 in ?? ()
#1 0x00007fc5fa465f82 in __nptl_deallocate_tsd () from
#2 0x00007fc5fa466197 in start_thread () from
#3 0x00007fc5fa19303d in clone () from /lib/x86_64-linux-gnu/