Bug 285502 - Crash when running KDIFF3
Summary: Crash when running KDIFF3
Status: RESOLVED NOT A BUG
Alias: None
Product: kompare
Classification: Applications
Component: general (show other bugs)
Version: 4.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kompare developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-01 19:14 UTC by Axel Krebs
Modified: 2011-11-01 19:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.25 KB, text/plain)
2011-11-01 19:20 UTC, Axel Krebs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Krebs 2011-11-01 19:14:57 UTC
Application: kompare (4.0.0)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic-pae i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

Just running KDIFF3 to compare two directories; 
Details:
- two Harddrisk drives
- each about 700000 files

PC has 8GB memory, 500 GB free space, 9 GB swap

The crash can be reproduced every time.

-- Backtrace:
Application: Kompare (kompare), signal: Aborted
[Current thread is 1 (Thread 0xb4efe710 (LWP 14298))]

Thread 2 (Thread 0xb20b7b70 (LWP 14308)):
#0  0xb5372d10 in __GI_clock_gettime (clock_id=1, tp=0xb20b7028) at ../sysdeps/unix/clock_gettime.c:116
#1  0xb60dc7d5 in do_gettime (frac=0xb20b7020, sec=0xb20b7018) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb61af4b6 in QTimerInfoList::updateCurrentTime (this=0xb1701a7c) at kernel/qeventdispatcher_unix.cpp:339
#4  0xb61af80a in QTimerInfoList::timerWait (this=0xb1701a7c, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0xb61ae053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb20b712c) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb61ae0ed in timerSourcePrepare (source=0xb1701a48, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb554888c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb5549637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb5549c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb61aeb37 in QEventDispatcherGlib::processEvents (this=0x8644960, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0xb617f1dd in QEventLoop::processEvents (this=0xb20b72b0, flags=...) at kernel/qeventloop.cpp:149
#12 0xb617f421 in QEventLoop::exec (this=0xb20b72b0, flags=...) at kernel/qeventloop.cpp:201
#13 0xb608290b in QThread::exec (this=0x8653908) at thread/qthread.cpp:498
#14 0xb615fe2d in QInotifyFileSystemWatcherEngine::run (this=0x8653908) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb60857b3 in QThreadPrivate::start (arg=0x8653908) at thread/qthread_unix.cpp:331
#16 0xb561fd31 in start_thread (arg=0xb20b7b70) at pthread_create.c:304
#17 0xb5e850ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb4efe710 (LWP 14298)):
[KCrash Handler]
#7  0xb77e3424 in __kernel_vsyscall ()
#8  0xb5de0c8f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0xb5de42b5 in __GI_abort () at abort.c:92
#10 0xb5fe04ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb5fde283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb5fde2bf in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb5fde464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb617f569 in QEventLoop::exec (this=0xbff26474, flags=...) at kernel/qeventloop.cpp:214
#15 0xb618419d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#16 0xb66da8f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#17 0x0804f8d6 in main (argc=) at ../../kompare/main.cpp:228

Possible duplicates by query: bug 284718, bug 284551, bug 284118, bug 284032, bug 283896.

Reported using DrKonqi
Comment 1 Axel Krebs 2011-11-01 19:20:38 UTC
Created attachment 65127 [details]
New crash information added by DrKonqi

kompare (4.0.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:

I observe still the same crash-behavior, even after rebooting

QUESTION Kompare is a programm to compare, right? Why d #I need to select a diff programm in settings?

-- Backtrace (Reduced):
#8  0xb5cf8c8f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0xb5cfc2b5 in __GI_abort () at abort.c:92
[...]
#14 0xb6097569 in QEventLoop::exec (this=0xbfd5a764, flags=...) at kernel/qeventloop.cpp:214
#15 0xb609c19d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#16 0xb65f28f4 in QApplication::exec () at kernel/qapplication.cpp:3760
Comment 2 Kevin Kofler 2011-11-01 19:44:47 UTC
You misunderstood what is meant by "diff program". That should not be a graphical diff viewer (which is what Kompare itself is), but just the plain old "diff". In fact, you don't have to fill in anything and it'll default to running just "diff". The option is such that you can fill in a full path to a different version of diff when needed.

Running anything other than a version of the command-line "diff" utility is not expected to work, in particular, KDiff3 is not suitable.