Hi Ken,
If you did compile with -g already, running "gdb `which inc` core" and
then getting a backtrace (using the "bt" command) would be helpful.
Actaully, that might be useful to get a function name even without
further debugging symbols.
Not directly relevant to Norm's trials, but are you aware of
coredumpctl(1)'s ‘info’ for systems that have that command?
$ coredumpctl info
PID: 6898 (qtox)
...
Signal: 6 (ABRT)
...
Stack trace of thread 6898:
#0 0x00007f1e936ec82f raise (libc.so.6)
#1 0x00007f1e936d7672 abort (libc.so.6)
#2 0x00007f1e93bf57fc _ZNK14QMessageLogger5fatalEPKcz
(libQt5C>
#3 0x00007f1e941ba83d
_ZN22QGuiApplicationPrivate25createPlatf>
#4 0x00007f1e941bacee
_ZN22QGuiApplicationPrivate21createEvent>
#5 0x00007f1e93df1405 _ZN23QCoreApplicationPrivate4initEv
(lib>
#6 0x00007f1e941bc580 _ZN22QGuiApplicationPrivate4initEv
(libQ>
#7 0x00007f1e9761c92a _ZN19QApplicationPrivate4initEv
(libQt5W>
#8 0x000056433bf6bf91 main (qtox)
#9 0x00007f1e936d8ce3 __libc_start_main (libc.so.6)
#10 0x000056433bf7039e _start (qtox)
--
Cheers, Ralph.