ptitSeb
Serial Porter
So I decided to work again on that right-click crash bug this Weekend. I started a gdb session with current build this saturday and find out that I had to rebuilt Qt (a special static lib build) with debug info to be ebble to go further in the debug
So I started rebuilding Qt.... It finished sunday afternoon... Than I had to cleanily recompile Telegram itself (because of changed PCH files)... It ended this monday morning.
So I quickly started a new debug session before going to work... to find out it doesn't crash anymore!
So I just took that binary, stripped it and create a new PND... Qt is a debug build, not a release build, but I don't think the missing optimisation is really important for that type of software.
Build 09
-----------
Here is the (short) gdb sesion
Code:
The program 'Telegram' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 1438 error_code 2 request_code 139 minor_code 51)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0x46588430 (LWP 29758) exited]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x45d88430 (LWP 29757)]
0x01291e6c in QAbstractEventDispatcher::registerTimer(int, Qt::TimerType, QObject*) ()
(gdb) bt
#0 0x01291e6c in QAbstractEventDispatcher::registerTimer(int, Qt::TimerType, QObject*) ()
#1 0x012c9994 in QObject::startTimer(int, Qt::TimerType) ()
#2 0x012d23f0 in QTimer::start() ()
#3 0x00fcf7c4 in QNetworkConfigurationManagerPrivate::startPolling() ()
#4 0x00fcfcd4 in QNetworkConfigurationManagerPrivate::updateConfigurations() ()
#5 0x0000000c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) info thread
Id Target Id Frame
17 Thread 0x4c2db430 (LWP 29782) "Qt HTTP thread" 0x43816620 in poll () from /lib/libc.so.6
15 Thread 0x49af1430 (LWP 29780) "MTP::internal::" 0x43816620 in poll () from /lib/libc.so.6
14 Thread 0x4a2f1430 (LWP 29770) "Qt HTTP thread" 0x43816620 in poll () from /lib/libc.so.6
12 Thread 0x4aaf1430 (LWP 29768) "MTP::internal::" 0x43816620 in poll () from /lib/libc.so.6
8 Thread 0x48783430 (LWP 29763) "QThread" 0xffff0520 in ?? ()
7 Thread 0x47f83430 (LWP 29762) "QThread" 0xffff0520 in ?? ()
5 Thread 0x46d88430 (LWP 29759) "QThread" 0xffff0520 in ?? ()
* 3 Thread 0x45d88430 (LWP 29757) "Qt bearer threa" 0x01291e6c in QAbstractEventDispatcher::registerTimer(int, Qt::TimerType, QObject*) ()
2 Thread 0x4497d430 (LWP 29756) "QXcbEventReader" 0x43816620 in poll () from /lib/libc.so.6
1 Thread 0x43e920a0 (LWP 29750) "Telegram" QMap<QString, WebImage*>::~QMap (this=0x20ef00c <(anonymous namespace)::webImages>, __in_chrg=<optimized out>) at ../../qt/include/QtCore/qmap.h:335
(gdb) qSo I quickly started a new debug session before going to work... to find out it doesn't crash anymore!
So I just took that binary, stripped it and create a new PND... Qt is a debug build, not a release build, but I don't think the missing optimisation is really important for that type of software.
Build 09
-----------
- Fixed right-click crash
Last edited:
