You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
авг 03 15:17:50 axet-laptop eiskaltdcpp-qt.desktop[1182356]: Catching signal : Segmentation fault
eiskaltdcpp-qt 2.4.2-1+b2
No more details yes. I just setup coredumps and hope I will catch it again.
Main issue would be having in-app signal handler, which prevents OS creating core dupms. This is technique when system app crashed, memory snapshot created, so later, it can run under gdb with loaded (additionally installed) debug symbols. And fullstack trace obtained.
Right now signals handled inside following files:
'./eiskaltdcpp-gtk/src/wulfor.cc' and './eiskaltdcpp-qt/src/main.cpp'
Would be better if singnal handlers only enabled for developer builds and for user systems it should be handled by the system.
The text was updated successfully, but these errors were encountered:
axet
changed the title
eiskaltdcpp-qt crashing
eiskaltdcpp-qt / gtk signal handlers
Aug 9, 2022
It happens on first run:
авг 03 15:17:50 axet-laptop eiskaltdcpp-qt.desktop[1182356]: Catching signal : Segmentation fault
eiskaltdcpp-qt 2.4.2-1+b2
No more details yes. I just setup coredumps and hope I will catch it again.
Main issue would be having in-app signal handler, which prevents OS creating core dupms. This is technique when system app crashed, memory snapshot created, so later, it can run under gdb with loaded (additionally installed) debug symbols. And fullstack trace obtained.
Right now signals handled inside following files:
'./eiskaltdcpp-gtk/src/wulfor.cc' and './eiskaltdcpp-qt/src/main.cpp'
Would be better if singnal handlers only enabled for developer builds and for user systems it should be handled by the system.
The text was updated successfully, but these errors were encountered: