Bug 238155 - Crash when closing KDevelop
Summary: Crash when closing KDevelop
Status: RESOLVED DUPLICATE of bug 267659
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 4.0.1
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 262108 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-19 12:21 UTC by Juan Ramírez Ruiz
Modified: 2011-08-27 16:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramírez Ruiz 2010-05-19 12:21:25 UTC
Application: kdevelop (4.0.0 (using KDevPlatform 1.0.0))
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
I just opened a session and closed it.
The application crashed at exit.

 -- Backtrace:
Application: KDevelop (kdevelop.bin), signal: Aborted
[Current thread is 1 (Thread 0xb787a710 (LWP 4331))]

Thread 3 (Thread 0xb4a37b70 (LWP 4332)):
#0  0x00efc422 in __kernel_vsyscall ()
#1  0x00393342 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0x003099f4 in __pthread_cond_timedwait (cond=0x908d818, mutex=0x908d800, abstime=0xb4a372b0) at forward.c:152
#3  0x00f6420f in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0x08b2d4e5 in ?? () from /usr/lib/libkdevplatformlanguage.so.1
#5  0x00f6332e in ?? () from /usr/lib/libQtCore.so.4
#6  0x0038e96e in start_thread (arg=0xb4a37b70) at pthread_create.c:300
#7  0x002fca0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb1335b70 (LWP 4338)):
#0  0x00efc422 in __kernel_vsyscall ()
#1  0x00309cf3 in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:95
#2  0x002a0697 in _L_lock_9637 () from /lib/tls/i686/cmov/libc.so.6
#3  0x0029eec6 in *__GI___libc_free (mem=0x933a640) at malloc.c:3736
#4  0x07d14fc6 in g_free () from /lib/libglib-2.0.so.0
#5  0x07d0bf5a in ?? () from /lib/libglib-2.0.so.0
#6  0x010920fd in QEventDispatcherGlib::~QEventDispatcherGlib() () from /usr/lib/libQtCore.so.4
#7  0x00f62e9a in ?? () from /usr/lib/libQtCore.so.4
#8  0x00f63336 in ?? () from /usr/lib/libQtCore.so.4
#9  0x0038e96e in start_thread (arg=0xb1335b70) at pthread_create.c:300
#10 0x002fca0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb787a710 (LWP 4331)):
[KCrash Handler]
#6  0x00efc422 in __kernel_vsyscall ()
#7  0x00259651 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0x0025ca82 in *__GI_abort () at abort.c:92
#9  0x0029049d in __libc_message (do_abort=2, fmt=0x364f58 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#10 0x0029a591 in malloc_printerr (action=<value optimized out>, str=0x6 <Address 0x6 out of bounds>, ptr=0x9504348) at malloc.c:6264
#11 0x0029bde8 in _int_free (av=<value optimized out>, p=<value optimized out>) at malloc.c:4792
#12 0x0029eecd in *__GI___libc_free (mem=0x9504348) at malloc.c:3738
#13 0x00eb9741 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0x02a4d9ec in rpp::Stream::~Stream() () from /usr/lib/libkdev4cpprpp.so.4.0.0
#15 0x0025e1bf in __run_exit_handlers (status=0, listp=0x385324, run_list_atexit=true) at exit.c:78
#16 0x0025e22f in *__GI_exit (status=0) at exit.c:100
#17 0x00245bde in __libc_start_main (main=0x804b5e0 <_start+240>, argc=1, ubp_av=0xbfe1cfd4, init=0x80512d0 <__libc_csu_init>, fini=0x80512c0 <__libc_csu_fini>, rtld_fini=0x2200c0 <_dl_fini>, 
    stack_end=0xbfe1cfcc) at libc-start.c:258
#18 0x0804b511 in _start ()

This bug may be a duplicate of or related to bug 227116.

Possible duplicates by query: bug 238117, bug 236011, bug 235466, bug 235132, bug 234228.

Reported using DrKonqi
Comment 1 Andreas Pakulat 2010-05-19 12:38:12 UTC
If this is reproduceable please run kdevelop in valgrind and provide the log.
Comment 2 Milian Wolff 2011-01-06 12:41:20 UTC
*** Bug 262108 has been marked as a duplicate of this bug. ***
Comment 3 Milian Wolff 2011-08-27 16:08:03 UTC

*** This bug has been marked as a duplicate of bug 267659 ***