https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #9 from michael ---
Go ahead and file sperrate bug for the new crash so its easier to track.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #8 from Mike Lothian ---
I'm still seeing a failure on master:
(lldb) run
Process 1098029 launched: '/usr/bin/kdiff3' (x86_64)
org.kde.kdiff3: Loading A: "/home/fireburn/dmesg.axion"
org.kde.kdiff3: Loading B: "/home/fireburn/dmesg.txt"
https://bugs.kde.org/show_bug.cgi?id=484988
michael changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=484988
michael changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #5 from Mike Lothian ---
I got a backtrace from kdiff3
git mergetool
Merging:
kcms/mouse/CMakeLists.txt
Normal merge conflict for 'kcms/mouse/CMakeLists.txt':
{local}: modified file
{remote}: modified file
(lldb) target create
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #4 from Mike Lothian ---
I've just checked, without the patch kdiff still doesn't crash if launched with
"kdiff3 /path/to/filea /path/to/fileb" only when it's "kdiff3 filea fileb"
It also aborts when using git mergetool:
git revert
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #3 from Mike Lothian ---
kdiff3 SQ-game8-sorted SQ-ign-sorted
org.kde.kdiff3: Loading A: "http://sq-game8-sorted;
kf.kio.core: mimeType() not emitted when sending first data!; job URL =
QUrl("http://sq-game8-sorted;) data size = 0
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #2 from Mike Lothian ---
So I notice this happens when running from the command line
kdiff3 filea fileb
It's assumign that filea & fileb are actually http://filea https://fileb and
saying they're binary equal
But works fine when giving
https://bugs.kde.org/show_bug.cgi?id=484988
--- Comment #1 from Mike Lothian ---
Created attachment 168106
--> https://bugs.kde.org/attachment.cgi?id=168106=edit
workaround
This works around the issue
--
You are receiving this mail because:
You are watching all bug changes.
