[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: konsole --version crashes



kamaraju kusumanchi ha scritto:
> On Thu, Dec 29, 2016 at 7:25 AM, Luigi Toscano <luigi.toscano@tiscali.it> wrote:
>>
>> When the backtrace starts, do you get the prompt of (gdb) again?
> 
> Yes. I get the prompt of (gdb) again.
> 
>> Try to type:
>>
>> (gdb) thread apply all backtrace
>>
>> and see if it gives you more output.
> 
> The output looks pretty much the same even with this command.
> 
> % gdb konsole
> ...
> Reading symbols from konsole...Reading symbols from
> /usr/lib/debug/.build-id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done.
> done.
> (gdb) set args --version
> (gdb) thread apply all backtrace
> (gdb) r
> Starting program: /usr/bin/konsole --version
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7fffe414b700 (LWP 9523)]
> [New Thread 0x7fffe2268700 (LWP 9524)]
> konsole 16.08.2
> 
> Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffe2268700 (LWP 9524)]
> 0x00007ffff44b03ef in QObject::disconnect (sender=0x5555557d7d90,
> signal=signal@entry=0x0,
>     receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0)
> at kernel/qobject.cpp:2956
> 2956    kernel/qobject.cpp: No such file or directory.
> (gdb) bt
> #0  0x00007ffff44b03ef in QObject::disconnect (sender=0x5555557d7d90,
> signal=signal@entry=0x0,
>     receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0)
> at kernel/qobject.cpp:2956
> #1  0x00007ffff7edfd50 in QObject::disconnect (member=0x0,
> receiver=0x7fffd40030f0, this=<optimized out>)
>     at ../../include/QtCore/../../src/corelib/kernel/qobject.h:336
> #2  QDBusConnectionPrivate::closeConnection
> (this=this@entry=0x7fffd40030f0) at qdbusintegrator.cpp:1145
> #3  0x00007ffff7ecc7e2 in QDBusConnectionManager::run (
>     this=0x7ffff7f41d60 <(anonymous
> namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
> qdbusconnection.cpp:188
> #4  0x00007ffff42b0da8 in QThreadPrivate::start (
>     arg=0x7ffff7f41d60 <(anonymous
> namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
> thread/qthread_unix.cpp:368
> #5  0x00007ffff0b16464 in start_thread (arg=0x7fffe2268700) at
> pthread_create.c:333
> #6  0x00007ffff78dd9df in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few race
conditions which requires some (unmerged) patches (unmerged because they cause
regression on windows), quoting:
"https://codereview.qt-project.org/180231 and 232 at least"

They are not apparently applied to the Qt packages in Debian.

Ciao
-- 
Luigi
> 
> 
>> Just to be sure: did you restart after the last updates (not only kernel, also
>> Qt)?
> 
> I did not do that before. But now I rebooted the computer and the
> backtrace above is what I get after the reboot.
> 
> thanks
> raju
> 


Reply to: