https://bugs.kde.org/show_bug.cgi?id=381636
David E. Narvaez changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=381636
--- Comment #6 from Giuseppe Della Bianca ---
Connection::~Connection()
{
delete mLogFile;
if (mSocket) {
mSocket->disconnect(this);
mSocket->close(); <
delete mSocket;
}
}
mSocket is
https://bugs.kde.org/show_bug.cgi?id=381636
--- Comment #5 from Giuseppe Della Bianca ---
My knowledge of Qt is less than zero.
I just noticed that QSocketNotifier object data contains abnormal or invalid
values.
The messages
'QSocketNotifier: Invalid socket 12 and type' Read ',
https://bugs.kde.org/show_bug.cgi?id=381636
--- Comment #4 from Christoph Feck ---
Funny, it only tries to print a qWarning, and crashes in strlen.
Thread 5 "QThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffb67ec700 (LWP 7741)]
0x7fffed147fe6
https://bugs.kde.org/show_bug.cgi?id=381636
--- Comment #3 from Giuseppe Della Bianca ---
Created attachment 106316
--> https://bugs.kde.org/attachment.cgi?id=106316=edit
output of akonadikonsole
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381636
--- Comment #2 from Giuseppe Della Bianca ---
Created attachment 106315
--> https://bugs.kde.org/attachment.cgi?id=106315=edit
gud-akonadikonsole
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381636
--- Comment #1 from Christoph Feck ---
Could you please try running it in gdb to obtain a backtrace?
> gdb akonadiconsole
> run
(reproduce crash)
> bt full
--
You are receiving this mail because:
You are watching all bug changes.