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

segmentation fault #11

Closed
yourilima opened this issue May 8, 2013 · 11 comments
Closed

segmentation fault #11

yourilima opened this issue May 8, 2013 · 11 comments

Comments

@yourilima
Copy link

Hi I just got a segmentation fault when hiding zeal
what i got is

youri:~/ $ zeal                                                       [9:23:24]
QEventLoop: Cannot be used without QApplication
[1]    2803 segmentation fault (core dumped)  zeal

My hiding keybinding is alt+d.
It happens only when im on a multimonitor setup.
I'm running arch with fluxbox.
I installed qt5 specifically for using zeal.

Im not sure where I can find more info or log messages.

thanks :) great job btw.

@yourilima
Copy link
Author

dmesg reports the following

[ 1219.728502] zeal[2833]: segfault at 8 ip 00007fc05c8619c0 sp 00007fff98d4c128 error 4 in libQt5Gui.so.5.0.2[7fc05c7a7000+3b4000]

@jmymay
Copy link
Member

jmymay commented May 8, 2013

Hi. Thank you for your report.

Can you try running

$ qmake CONFIG+=debug

then recompiling (make) and running

$ gdb zeal

and in gdb prompt enter:

(gdb) run

(just type 'run' after '(gdb)'), then "Program received signal SIGSEGV, Segmentation fault." should appear. When it does, in the gdb prompt again type:

(gdb) where

and paste the output here.

@yourilima
Copy link
Author

There

youri:zeal/ (master) $ gdb zeal                                                                                                                                                                                                                                        [15:19:20]
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /var/dev/build/zeal/zeal/zeal...done.
(gdb) run
Starting program: /var/dev/build/zeal/zeal/zeal 
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe9a46700 (LWP 26912)]
[New Thread 0x7fffe2f79700 (LWP 26913)]
[New Thread 0x7fffda194700 (LWP 26914)]
[New Thread 0x7fff9708d700 (LWP 26915)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff3df09c0 in QPlatformWindow::window() const () from /usr/lib/libQt5Gui.so.5
(gdb) where
#0  0x00007ffff3df09c0 in QPlatformWindow::window() const () from /usr/lib/libQt5Gui.so.5
#1  0x00007fffe3d93dc2 in ?? () from /usr/lib/qt/plugins/platforms/libqxcb.so
#2  0x00007fffe3d8f652 in ?? () from /usr/lib/qt/plugins/platforms/libqxcb.so
#3  0x00007fffe3d9032b in ?? () from /usr/lib/qt/plugins/platforms/libqxcb.so
#4  0x00007ffff396314e in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#5  0x00007ffff4be48dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#6  0x00007ffff4be95f2 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#7  0x00007ffff393e2fd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#8  0x00007ffff393fad7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#9  0x00007ffff3982d33 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x00007ffff032df06 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff032e258 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007ffff032e2fc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#13 0x00007ffff39829fc in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#14 0x00007ffff393d1ab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#15 0x00007ffff39422b1 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#16 0x0000000000416a1f in main (argc=1, argv=0x7fffffffe088) at main.cpp:23

@jmymay
Copy link
Member

jmymay commented May 8, 2013

Thanks. Please try recompiling with 3ca6dda.

UPDATE: I've noticed it still crashes sometimes. Sorry, debugging requires more time, which I don't have at the moment. Hopefully it crashes less often at least...

@jmymay
Copy link
Member

jmymay commented May 8, 2013

I think it's now mostly fixed in 018f3e8. (I've managed to get some different SIGSEGV in Arch in VirtualBox after lots of hiding/showing, but can't find a way to reliably reproduce it. If you can, please let me know. My fingers are aching from testing already, and it seems rather stable for me. :))

Anyway, it seems to have been introduced by Qt 5.0.2 somehow - I haven't seen these SIGSEGVs with 5.0.1.

@yourilima
Copy link
Author

Ok thank you very much. its a day off for us. and i dont have the multimonitor setup at home here. but I'll let you know tomorrow how it goes :) 👍

@yourilima
Copy link
Author

great have not been able to reproduce anymore. fixed
thanks.

@stardiviner
Copy link

I got this issue again.
I tried to remove all docsets. still got this error.
Also tried to remove ~/.local/share/Zeal and ~/.config/Zeal. Still got this error.
I install Zeal from Arch Linux AUR. I tried both packages zeal and zeal-git.

@trollixx
Copy link
Member

trollixx commented Oct 8, 2016

@stardiviner, are you sure you have got this issue and not #595/#605?

@stardiviner
Copy link

@trollixx, sorry, my problem is exactly same with #595

@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related requests.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

4 participants