Bug 75917 - Incorrectly shows no-differences when there are; & crashes on some files when doing a dir diff
Summary: Incorrectly shows no-differences when there are; & crashes on some files when...
Status: RESOLVED NOT A BUG
Alias: None
Product: kompare
Classification: Applications
Component: parser (show other bugs)
Version: 3.2
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Kompare developers
URL:
Keywords:
: 83548 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-23 13:53 UTC by Adrian Head
Modified: 2009-01-04 15:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
One of the files where kompare does fail (10.45 KB, text/plain)
2004-11-29 21:10 UTC, Eric L.
Details
The other file where kompare does fail (10.45 KB, text/plain)
2004-11-29 21:11 UTC, Eric L.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Head 2004-02-23 13:53:49 UTC
Version:           3.2 (using KDE KDE 3.2.0)
Installed from:    Gentoo Packages
OS:          Linux

It appears that some files will cause kompare to show no differences when there are some.  This seems to happen on quite a few files but the results are always the same.  kompare even when pointed to the affected individual files follows this behaviour.  Sometimes I have seen occurances where for example I'm diff'ing vers 1.3 & 1.4 files; kompare will mistakenly show the top of the file as the 1.4 file but the body of the file will be 1.3.

When doing a full directory diff - the same problems occur; however, when clicking on certain files kompare will crash.  I don't have a useful trace but will attempt to provide one if required.

The kompare version that came with KDE3.1.5 does not show this behaviour and shows differences correctly without crashing.

Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3-gentoo-r1)
=================================================================
System uname: 2.6.3-gentoo-r1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.4.3.13
CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CXXFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer"
Comment 1 Adrian Head 2004-02-23 14:30:34 UTC
I forgot the other important thing:
diff --version
diff (GNU diffutils) 2.8.4
Copyright (C) 2002 Free Software Foundation, Inc.
Comment 2 Otto Bruggeman 2004-02-24 11:22:49 UTC
A bit of debug info from the konsole output would be nice plus a backtrace with debugsymbols, put it in a file and attach it to this report, thank you for reporting the bug.
Comment 3 Adrian Head 2004-03-02 05:34:41 UTC
I've found another directory that crashes kompare - here is the console dump and backtrace.

Console Dump:
akh@heady akh $ kompare
kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-akh/ksycoca
kio (KTrader): KServiceTypeProfile::offers( text/x-diff,Kompare/ViewPart )
kio (KTrader): Returning 1 offers
kompare: : KDockWidget::setHeader
kompare: KDockWidgetHeader::showUndockButton(true)
kparts: ReadWritePart::setModified( false)
kparts: DockMainWindow::createGUI for kompare_part
kio (KTrader): KServiceTypeProfile::offers( text/x-diff,KParts/ReadOnlyPart )
kio (KTrader): Returning 8 offers
kompare: : KDockWidget::setHeader
kompare: KDockWidgetHeader::showUndockButton(true)
kompare: : KDockWidget::setHeader
kompare: KDockWidgetHeader::showUndockButton(true)
kio (KDirWatch): Can't use FAM (fam daemon not running?)
kio (KDirWatch): Available methods: Stat, DNotify
kio (KDirWatch): addDir - recursive/watchFiles not supported in KDE 3.0
kio (KDirWatch): Added Dir /home/akh/develop/demo_working/demo_prod [dirwatch]
kio (KDirWatch):  Setup DNotify (fd 128) for /home/akh/develop/demo_working/demo_prod
kio (KDirWatch): addDir - recursive/watchFiles not supported in KDE 3.0
kio (KDirWatch): Added Dir /home/akh/develop/demo_working/demoweb [dirwatch]
kio (KDirWatch):  Setup DNotify (fd 129) for /home/akh/develop/demo_working/demoweb

===== (Point of Crash) =====

Backtrace from KDE Crash Handler:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 15170)]
0x41107688 in waitpid () from /lib/libpthread.so.0
#0  0x41107688 in waitpid () from /lib/libpthread.so.0
#1  0x4082a22c in __JCR_LIST__ () from /usr/kde/3.2/lib/libkdecore.so.4
#2  0x40777a52 in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:246
#3  0x41106405 in __pthread_sighandler () from /lib/libpthread.so.0
#4  <signal handler called>
#5  0x417b23d4 in KompareNavTreePart::slotFileListSelectionChanged(QListViewItem*) () from /usr/kde/3.2/lib/kde3/libkomparenavtreepart.so
#6  0x08195780 in ?? ()

The question I have is - is this backtrace useful?  It looks better than others I have seen in the fact there are no "unknown symbols" but do you require more information?
Comment 4 Otto Bruggeman 2004-03-03 20:20:49 UTC
The backtrace is not very useful, if you could reconfigure kdesdk with the --enable-debug=full option and then recompile kdesdk (after a make clean in that directory) that would be really useful. The debug output is also not very useful, all the interesting stuff is not being printed (perhaps you can check with kdebugdialog --fullmode and redirect all output for areas 8100-8106 to a file and attach it here). Thanks for following up and sorry for replying so late, i've been too busy)
Comment 5 Adrian Head 2004-03-10 08:23:57 UTC
Now that KDE 3.2.1 is out - I'll compile that and see if the problems still exist and during the compile I'll turn on --enable-debug=full.  I'll also have a look at kdebugdialog --fullmode at the same time.

Thanks for your time.
Comment 6 Otto Bruggeman 2004-03-27 18:24:53 UTC
We found the cause, just dont use -B and -b while diffing to get around the crashes. I'll fix this as soon as possible.
Comment 7 Otto Bruggeman 2004-08-21 17:37:40 UTC
*** Bug 83548 has been marked as a duplicate of this bug. ***
Comment 8 Eric L. 2004-11-29 21:10:32 UTC
Created attachment 8488 [details]
One of the files where kompare does fail
Comment 9 Eric L. 2004-11-29 21:11:20 UTC
Created attachment 8489 [details]
The other file where kompare does fail
Comment 10 Eric L. 2004-11-29 21:20:08 UTC
Hi,

sorry for the multiple emails, but there doesn't seem to be a way to add attachments and put comment at once...
I have a very similar problem under Debian Sarge, using kompare 3.2.1 under KDE 3.2.3. When I compare the two attached files, I don't see any difference, though kompare does say there are 16 of them. If I swap source with destination, 6 out of 16 are shown. If I reswap the files, I get a nice SIGFPE each time.

Some more remarks:
- diff --version : diff (GNU diffutils) 2.8.1
- in Diff settings -> options, only the options "Look for smaller changes" and "optimize for large files" are set (I think, that means -B and -b are not set).
- unsetting these 2 options didn't help.

Thanks, Eric
Comment 11 Jeff Snyder 2004-11-30 13:59:26 UTC
jeff@obsidian bug $ ls
attachment.cgi?id=8488&action=view  attachment.cgi?id=8489&action=view
jeff@obsidian bug $ md5sum *
eeb8616687ebc08c376d6eebc0e5c02b  attachment.cgi?id=8488&action=view
eeb8616687ebc08c376d6eebc0e5c02b  attachment.cgi?id=8489&action=view

These files are identical. can you please upload the other one?

- Jeff
Comment 12 Jeff Snyder 2005-06-06 21:44:55 UTC
This is gonna be a little spammy... I'm reassigning everything that's currently 
assigned to bruggie (who's been the default assignee for bugs since time began) 
to the new list address. 
 
Bruggie: if you're working on one or more of these atm, please snatch 'em 
back.. 
 
Everyone, esp. Joshua and Bruggie: if this genrates 33 mails, my sincere 
apologies.. 
Comment 13 FiNeX 2009-01-04 15:14:58 UTC
Closing due to absence of feedback since 5 years, the two files are identical and kompare works fine with them.