Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eiskaltdcpp-qt / gtk signal handlers #488

Open
axet opened this issue Aug 4, 2022 · 0 comments
Open

eiskaltdcpp-qt / gtk signal handlers #488

axet opened this issue Aug 4, 2022 · 0 comments

Comments

@axet
Copy link

axet commented Aug 4, 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.

@axet axet changed the title eiskaltdcpp-qt crashing eiskaltdcpp-qt / gtk signal handlers Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant