Summary: | crash on startup because of segmentation fault (SKGmainPanel::displayMessage) | ||
---|---|---|---|
Product: | [Applications] skrooge | Reporter: | Gilles Habran <gilleshabran> |
Component: | general | Assignee: | Stephane MANKOWSKI <stephane> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | crash | CC: | cedeel, smaudet, stephane |
Priority: | NOR | ||
Version: | 1.12 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Complete log from KDE Crash Handler
t.txt (skgtrace 10) New crash information added by DrKonqi |
Description
Gilles Habran
2015-05-20 22:07:30 UTC
Created attachment 92747 [details]
Complete log from KDE Crash Handler
Hi, This crash is very strange. I don't really understand why some libraries of Skrooge are built in debug mode (libskgbasegui.so) and some other not (skg_file.so). This could help me if you are able to build all libraries in debug mode to have a better call stack. Could you try to do that too? export SKGTRACE=10 skrooge --nofork > t.txt 2>&1 And send me t.txt Thank you. Created attachment 92773 [details]
t.txt (skgtrace 10)
Used to get the file :
export SKGTRACE=10
skrooge --nofork > t.txt 2>&1
I just tried to compile skrooge (source from git) in debug mode with cmake and launch it and it works. Should I try to compile the source from git in release mode and manually install it on my system ? The one I download from the arch repository does not work. I have the file t.txt from the debug binary that works. I think the crash was due to unaligned libraries. If you build skrooge in release mode and install it then this should work correctly. I close this incident. Reopen it if needed. *** Bug 348116 has been marked as a duplicate of this bug. *** Created attachment 97230 [details]
New crash information added by DrKonqi
skrooge (1.11.0) on KDE Platform 4.14.7 using Qt 4.8.6
- What I was doing when the application crashed:
startup from krunner
Would like to re-open the parent bug, reading through the logs it doesn't appear anything was fixed.
-- Backtrace (Reduced):
#6 QWidget::layout (this=0x100f602f6020300) at kernel/qwidget.cpp:9780
#7 0x00007f60ee343de9 in SKGMainPanel::displayMessage (this=0x2423b50, iMessage=..., iType=SKGDocument::Error) at /usr/src/debug/skrooge-1.11.0/skgbasegui/skgmainpanel.cpp:2212
#8 0x00007f60ee343c10 in SKGMainPanel::displayErrorMessage (this=this@entry=0x2423b50, iMessage=...) at /usr/src/debug/skrooge-1.11.0/skgbasegui/skgmainpanel.cpp:2243
#9 0x00007f60ee34515e in SKGMainPanel::displayErrorMessage (iError=..., iAction=iAction@entry=0x0) at /usr/src/debug/skrooge-1.11.0/skgbasegui/skgmainpanel.cpp:2254
#10 0x00007f607f9a94ee in SKGFilePlugin::onNew (this=this@entry=0x283e7f0) at /usr/src/debug/skrooge-1.11.0/plugins/generic/skg_file/skgfileplugin.cpp:300
Hi Sebastian, This incident has not been fixed because it was due to a bad alignment of libraries. Means, that skrooge has been built on a version of KDE/Qt and the user tried to run it on a new version of KDE/Qt. To be sure, could you try rebuild Skrooge? I think you won't have the issue anymore. |