Bug 339002

Summary: I'm still getting the error "The diff is malformed. Some lines could not be parsed and will not be displayed in the diff view." when komparing two large source trees
Product: [Applications] kompare Reporter: Mathias Homann <Mathias.Homann>
Component: parserAssignee: Kompare developers <kompare-devel>
Status: RESOLVED DUPLICATE    
Severity: major CC: giluxxx
Priority: NOR    
Version: 4.1.3   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: a recursive diff that kompare complains about

Description Mathias Homann 2014-09-11 08:02:46 UTC
When I try to kompare two big source trees, I get the error:
"The diff is malformed. Some lines could not be parsed and will not be displayed in the diff view."

kompare gives me NO indication of which files in the trees are the culprits.


Reproducible: Always

Steps to Reproduce:
1. Check out this source: https://bitbucket.org/marinekelley/rlv
2. Check out this source: https://bitbucket.org/lindenlab/viewer-release
3. use kompare on these two trees

Actual Results:  
I get that error message, and I can't be sure if i actually see all differences or not

Expected Results:  
I would expect kompare to either parse the diff properly, or tell me what the cause for the problem is.
Comment 1 Mathias Homann 2014-09-11 08:06:39 UTC

*** This bug has been marked as a duplicate of bug 249976 ***
Comment 2 giluxxx 2016-04-21 11:39:03 UTC
i see this happening too when comparing 2 folders (2 git branches) (so has nothing to do with svn output that supposedly the duplicate is about)
Comment 3 Mathias Homann 2020-06-29 08:28:41 UTC
This is definitely not fixed, and the two trees by now are git so it's unlikely to be because of a .svn folder...

Attached is a "diff -burNE --exclude=.git" that, when piped into a file and then opened in kompare, gives me the "malformed diff" issue.
Comment 4 Mathias Homann 2020-06-29 08:29:47 UTC
Created attachment 129753 [details]
a recursive diff that kompare complains about
Comment 5 Kevin Kofler 2020-06-29 09:18:35 UTC
Still a duplicate though.

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