You are not logged in.
- Topics: Active | Unanswered
#1 2007-08-08 10:40:24
- lloeki
- Member
- From: France
- Registered: 2007-02-20
- Posts: 456
- Website
kdevelop sigseg on exit, sigalrm anytime: libc fault?
kdevelop 95% of times crashes on exit. that's kdemod version (which is different only in depending on kdemod-kdesdk). anyone else experiences this?
looking at the backtrace, not the same parts are involved (here it's kate related, but kate itself is rock solid, and sometimes it's other) but the part ALWAYS involved is:
#6 0xb634a6b3 in malloc_consolidate () from /lib/libc.so.6
#7 0xb634c035 in _int_free () from /lib/libc.so.6
#8 0xb634c2a9 in free () from /lib/libc.so.6here's the gdb backtrace, as given by the crash handler:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...cut no deb symbols...]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1250609424 (LWP 12289)]
(no debugging symbols found)
[...cut no deb symbols...]
(no debugging symbols found)
[KCrash handler]
#6 0xb634a6b3 in malloc_consolidate () from /lib/libc.so.6
#7 0xb634c035 in _int_free () from /lib/libc.so.6
#8 0xb634c2a9 in free () from /lib/libc.so.6
#9 0xb64f84d1 in operator delete () from /usr/lib/libstdc++.so.6
#10 0xb64f852d in operator delete[] () from /usr/lib/libstdc++.so.6
#11 0xb41fcae0 in KateFontMetrics::~KateFontMetrics ()
from /opt/kde/lib/kde3/libkatepart.so
#12 0xb41fcb40 in KateFontStruct::~KateFontStruct ()
from /opt/kde/lib/kde3/libkatepart.so
#13 0xb420ff44 in KateRendererConfig::~KateRendererConfig ()
from /opt/kde/lib/kde3/libkatepart.so
#14 0xb421c7cf in KateFactory::~KateFactory ()
from /opt/kde/lib/kde3/libkatepart.so
#15 0xb42db4bf in KStaticDeleter<KateFactory>::destructObject ()
from /opt/kde/lib/kde3/libkatepart.so
#16 0xb6eb5a7b in KGlobal::deleteStaticDeleters ()
from /opt/kde/lib/libkdecore.so.4
#17 0xb6f6f692 in KApplication::~KApplication ()
from /opt/kde/lib/libkdecore.so.4
#18 0x0804e582 in ?? ()
#19 0xbfa8e840 in ?? ()
#20 0x00000001 in ?? ()
#21 0xbfa8e9d0 in ?? ()
#22 0x00000001 in ?? ()
#23 0x08052c37 in ?? ()
#24 0x00000001 in ?? ()
#25 0x08052d30 in ?? ()
#26 0x08052489 in ?? ()
#27 0x0805249e in ?? ()
#28 0x0805248a in ?? ()
#29 0x2b43e9ed in ?? ()
#30 0x00000042 in ?? ()
#31 0x080641b0 in ?? ()
#32 0xb7904020 in ?? ()
#33 0xb634c31e in _int_malloc () from /lib/libc.so.6
#34 0xb62fa970 in __libc_start_main () from /lib/libc.so.6
#35 0x0804d731 in ?? ()this is getting annoying.
EDIT: and sometimes, that's a SIGABRT, happening anytime. backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...snip]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1250580752 (LWP 12567)]
[New Thread -1262351472 (LWP 12572)]
(no debugging symbols found)
[...snip]
(no debugging symbols found)
0xb7f55410 in __kernel_vsyscall ()
#0 0xb7f55410 in __kernel_vsyscall ()
#1 0xb63b990e in __lll_mutex_lock_wait () from /lib/libc.so.6
#2 0xb635602c in _L_lock_3440 () from /lib/libc.so.6
#3 0xb635329d in free () from /lib/libc.so.6
#4 0xb64ff4d1 in operator delete () from /usr/lib/libstdc++.so.6
#5 0xb68b9c26 in QPtrList<QSockNot>::deleteItem ()
from /opt/qt/lib/libqt-mt.so.3
#6 0xb6bc7599 in QGList::remove () from /opt/qt/lib/libqt-mt.so.3
#7 0xb68b92ca in QEventLoop::unregisterSocketNotifier ()
from /opt/qt/lib/libqt-mt.so.3
#8 0xb693faef in QSocketNotifier::setEnabled ()
from /opt/qt/lib/libqt-mt.so.3
#9 0xb6874e51 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3
#10 0xb68dacd0 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3
#11 0xb68dab66 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3
#12 0xb68c416f in QApplication::exec () from /opt/qt/lib/libqt-mt.so.3
#13 0x0804e50a in ?? ()
#14 0xbfc7c9e0 in ?? ()
#15 0x0808fb40 in ?? ()
#16 0xbfc7cb70 in ?? ()
#17 0x00000001 in ?? ()
#18 0x08052c37 in ?? ()
#19 0x00000001 in ?? ()
#20 0x08052d30 in ?? ()
#21 0x08052489 in ?? ()
#22 0x0805249e in ?? ()
#23 0x0805248a in ?? ()
#24 0x2b43e9ed in ?? ()
#25 0x00000042 in ?? ()
#26 0x080641b0 in ?? ()
#27 0xb790b020 in ?? ()
#28 0xb635331e in _int_malloc () from /lib/libc.so.6
#29 0xb6301970 in __libc_start_main () from /lib/libc.so.6
#30 0x0804d731 in ?? ()Last edited by lloeki (2007-08-08 10:53:44)
To know recursion, you must first know recursion.
Offline
#2 2007-08-11 21:03:21
- damunix
- Member
- Registered: 2007-06-30
- Posts: 12
Re: kdevelop sigseg on exit, sigalrm anytime: libc fault?
same problem hear !
Offline
#3 2007-08-12 12:52:08
- Cerebral
- Forum Fellow
- From: Waterloo, ON, CA
- Registered: 2005-04-08
- Posts: 3,108
- Website
Re: kdevelop sigseg on exit, sigalrm anytime: libc fault?
This seems to be a known bug in Kdevelop 3.4.1 - they've released a stable snapshot build which (looking at the fixed bug list) seems to have this problem fixed. I'm trying to get in contact with the kdevelop devs right now to figure out how to get the sources for that stable build.
Offline
#4 2007-08-12 18:41:02
- Cerebral
- Forum Fellow
- From: Waterloo, ON, CA
- Registered: 2005-04-08
- Posts: 3,108
- Website
Re: kdevelop sigseg on exit, sigalrm anytime: libc fault?
I'm uploading a new kdevelop package to testing based off a stable repo snapshot. Once it's up, can you try it out and let me know whether it solves your problem or not?
Offline
#5 2007-08-14 12:27:57
- lloeki
- Member
- From: France
- Registered: 2007-02-20
- Posts: 456
- Website
Re: kdevelop sigseg on exit, sigalrm anytime: libc fault?
well, I'll try to have a look, but I'm using kdemod. I don't know if I can mix them with kdemod-kdesdk, or if I can mix kdesdk from current/extra with kdemod, but I'll try to hack around.
To know recursion, you must first know recursion.
Offline
#6 2007-08-14 16:51:50
- lloeki
- Member
- From: France
- Registered: 2007-02-20
- Posts: 456
- Website
Re: kdevelop sigseg on exit, sigalrm anytime: libc fault?
tried that one:
testing/kdevelop 3.4.1.20070730-1It gave me this:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...zap]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1250452736 (LWP 9410)]
[KCrash handler]
#6 malloc_consolidate (av=0xb6438120) at malloc.c:4830
#7 0xb6371655 in _int_free (av=0xb6438120, mem=0x824df20) at malloc.c:4715
#8 0xb63718c9 in *__GI___libc_free (mem=0x824df20) at malloc.c:3622
#9 0xb6242eca in XftFontDestroy () from /usr/lib/libXft.so.2
#10 0xb624309a in XftFontManageMemory () from /usr/lib/libXft.so.2
#11 0xb624008c in _XftCloseDisplay () from /usr/lib/libXft.so.2
#12 0xb65d2e3d in XCloseDisplay () from /usr/lib/libX11.so.6
#13 0xb687d0ed in qt_cleanup () from /opt/qt/lib/libqt-mt.so.3
#14 0xb68ef310 in QApplication::~QApplication ()
from /opt/qt/lib/libqt-mt.so.3
#15 0xb6f9b8b9 in KApplication::~KApplication ()
from /opt/kde/lib/libkdecore.so.4
#16 0x0804e559 in ?? ()
#17 0xbfd30430 in ?? ()
#18 0x00000001 in ?? ()
#19 0xbfd305c0 in ?? ()
#20 0x00000001 in ?? ()
#21 0x08052b97 in ?? ()
#22 0x00000001 in ?? ()
#23 0x08052c90 in ?? ()
#24 0x080523e9 in ?? ()
#25 0x080523fe in ?? ()
#26 0x080523ea in ?? ()
#27 0xb7f5869f in do_lookup_x (new_hash=134542432, old_hash=0xbfd305c8,
ref=0xb7f69ca0, result=0x8052320, scope=0xbfd30668, i=3056730000,
flags=-1076689260, skip=0xbfd3069c) at do-lookup.h:196
#28 0xb631ff90 in __libc_start_main (main=0x804d7c0 <__gmon_start__@plt+172>,
argc=1, ubp_av=0xbfd30694, init=0x8052320, fini=0x8052310,
rtld_fini=0xb7f5cd60 <_dl_fini>, stack_end=0xbfd3068c) at libc-start.c:222
#29 0x0804d751 in ?? ()To know recursion, you must first know recursion.
Offline
#7 2007-08-14 17:06:14
- Cerebral
- Forum Fellow
- From: Waterloo, ON, CA
- Registered: 2005-04-08
- Posts: 3,108
- Website
Re: kdevelop sigseg on exit, sigalrm anytime: libc fault?
Crap... looks like it's happening at program close again - is the SIGABRT gone at least (as near as you can tell)?
Offline