Summary: | Crash when running KDIFF3 | ||
---|---|---|---|
Product: | [Applications] kompare | Reporter: | Axel Krebs <axel.krebs> |
Component: | general | Assignee: | Kompare developers <kompare-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | axel.krebs |
Priority: | NOR | ||
Version: | 4.0.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Axel Krebs
2011-11-01 19:14:57 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
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. |