Bug 120835 - kopete segfaults for (so far) unknown reason
Summary: kopete segfaults for (so far) unknown reason
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-26 23:04 UTC by Jerry Kilpatrick
Modified: 2006-03-24 11:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerry Kilpatrick 2006-01-26 23:04:31 UTC
Version:           0.11.0 (using KDE KDE 3.5.0)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) CFLAGS="-march=athlon -O3 -pipe -fomit-frame-pointer"
OS:                Linux

This happens to me at least twice a day.  I haven't been able to track down what is causing it and I can't purposfully reproduce it.  I did however attach gdb to the process and caught a crash this last time so I hope you can help me.

I can say that it generally happens after it has been idle.

Lastly before I give you the BT I'll have to admit to you that I use kopete over a broadband connection via openssh x11 forwarding.  As far as I understand this "shouldn't" be a problem but then again I could be very wrong.

Plugins Loaded:
History

Backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 8143)]
0xb600c37b in strlen () from /lib/libc.so.6

(gdb) bt
#0  0xb600c37b in strlen () from /lib/libc.so.6
#1  0xb6c0defc in QString::endsWith () from /usr/qt/3/lib/libqt-mt.so.3
#2  0xb6c0c1fa in QString::fromLatin1 () from /usr/qt/3/lib/libqt-mt.so.3
#3  0xb6fdb3d7 in KURL::KURL () from /usr/kde/3.5/lib/libkdecore.so.4
#4  0x08686bf0 in ?? ()
#5  0xbff45860 in ?? ()
#6  0x08282c30 in ?? ()
#7  0xb6008c71 in mallopt () from /lib/libc.so.6
Previous frame inner to this frame (corrupt stack?)

I will gladly give more information as it is needed.
Comment 1 Matt Rogers 2006-01-27 02:01:19 UTC
Can you recompile with debug information (FEATURES="nostrip" USE="debug" emerge ...) and repost the backtrace? Also, make sure you take -fomit-frame-pointer out of your CFLAGS as that kills any hope of getting a valid backtrace.
Comment 2 Jerry Kilpatrick 2006-02-06 21:57:38 UTC
I went through a dry spell where I was having no crashes but they've come back in full force.  I still have no idea what is causing them but here's my backtrace.

(gdb) bt
#0  0xb603337b in strlen () from /lib/libc.so.6
#1  0xb6c46efc in QString::endsWith () from /usr/qt/3/lib/libqt-mt.so.3
#2  0xb6c451fa in QString::fromLatin1 () from /usr/qt/3/lib/libqt-mt.so.3
#3  0xb7014757 in KURL::KURL () from /usr/kde/3.5/lib/libkdecore.so.4
#4  0x4a484452 in ?? ()
Comment 3 Olivier Goffart 2006-03-10 23:19:31 UTC
Not really usefull backtrace....
It doesn't even show kopete calls

what appears in the debug output ?
Comment 4 Olivier Goffart 2006-03-24 11:05:00 UTC
We can do anything without more information
Please reopen if you can give us step to reproduce, or a meaningfull backtrace.