Bug 1033186

Summary: [abrt] kompare: QString::QString(): kompare killed by SIGSEGV
Product: [Fedora] Fedora Reporter: KitchM <tech>
Component: kompareAssignee: Kevin Kofler <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dvratil, get.sonic, jgrulich, jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, tech, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fb73d9d846a83ce4fd2ae704778d5a755e0f428d
Whiteboard: abrt_hash:55fc7f487c2235a6a5d1e853ac722dcf6ccab03e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:20:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description KitchM 2013-11-21 16:27:27 UTC
Version-Release number of selected component:
kompare-4.11.3-1.fc19

Additional info:
reporter:       libreport-2.1.9.20.g0f25
backtrace_rating: 4
cmdline:        kompare -caption Kompare -o
crash_function: QString::QString
executable:     /usr/bin/kompare
kernel:         3.11.8-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 QString::QString at tools/qstring.cpp:1060
 #3 qulltoa at tools/qlocale_tools.cpp:108
 #4 qlltoa at tools/qlocale_tools.cpp:113
 #5 QLocalePrivate::longLongToString at tools/qlocale.cpp:2671
 #7 QString::setNum at tools/qstring.cpp:5952
 #8 setNum at ../../src/corelib/tools/qstring.h:734
 #9 QString::number at tools/qstring.cpp:6078
 #10 KIconLoaderPrivate::makeCacheKey at /usr/src/debug/kdelibs-4.11.3/kdeui/icons/kiconloader.cpp:764
 #11 KIconLoader::loadIcon at /usr/src/debug/kdelibs-4.11.3/kdeui/icons/kiconloader.cpp:1116
 #12 SmallIcon at /usr/src/debug/kdelibs-4.11.3/kdeui/icons/kiconloader.cpp:1530

Comment 1 KitchM 2013-11-21 16:28:08 UTC
Created attachment 827336 [details]
File: backtrace

Comment 2 KitchM 2013-11-21 16:28:13 UTC
Created attachment 827337 [details]
File: cgroup

Comment 3 KitchM 2013-11-21 16:28:22 UTC
Created attachment 827338 [details]
File: core_backtrace

Comment 4 KitchM 2013-11-21 16:28:28 UTC
Created attachment 827339 [details]
File: dso_list

Comment 5 KitchM 2013-11-21 16:28:32 UTC
Created attachment 827340 [details]
File: environ

Comment 6 KitchM 2013-11-21 16:28:36 UTC
Created attachment 827341 [details]
File: exploitable

Comment 7 KitchM 2013-11-21 16:28:40 UTC
Created attachment 827342 [details]
File: limits

Comment 8 KitchM 2013-11-21 16:28:44 UTC
Created attachment 827343 [details]
File: maps

Comment 9 KitchM 2013-11-21 16:28:48 UTC
Created attachment 827344 [details]
File: open_fds

Comment 10 KitchM 2013-11-21 16:28:52 UTC
Created attachment 827345 [details]
File: proc_pid_status

Comment 11 KitchM 2013-11-21 16:28:55 UTC
Created attachment 827346 [details]
File: var_log_messages

Comment 12 Kevin Kofler 2013-11-30 00:31:33 UTC
Looks like a corrupt KDE icon cache. Don't ask me why it sometimes happens, but the icon cache sometimes goes corrupt. It's kdelibs' fault and not Kompare's, not that it changes all that much for you.

Try deleting the ~/.kde/cache-*/icon-cache.kcache file.

Comment 13 Kevin Kofler 2013-11-30 00:35:43 UTC
Whoops, nevermind… Looking at the full backtrace, this is NOT the icon cache's fault, but infinite recursion at komparenavtreepart.cpp:674 inside Kompare.

Comment 14 Kevin Kofler 2013-11-30 23:48:26 UTC
Can you please attach the input files which cause this bug (or e-mail them directly to me if you don't want them public)?

Comment 15 KitchM 2013-12-01 02:27:54 UTC
What files are those, and where do I find them?

Comment 16 Kevin Kofler 2013-12-01 03:03:28 UTC
What diff/patch file did you open, or what files did you compare?

Comment 17 KitchM 2013-12-01 05:03:57 UTC
I have no clue at this time.

Comment 18 Kevin Kofler 2013-12-01 12:21:51 UTC
That's too bad. :-(

The source of the crash is that somehow, in the directory tree view, a folder ends up being its own child, or at least the recursion that walks the directories incorrectly thinks so. So I wonder how this can happen, the input file would have helped a lot. :-( Please let me know if you see this happening again.

I'll try to figure out anyway what's going on, but without the reproducing diff, it's going to be hard, unfortunately.

Comment 19 KitchM 2013-12-01 14:40:03 UTC
I'll watch for it again.

Comment 20 Syam 2013-12-06 17:42:07 UTC
I can reproduce the crash at will. I tried to compare Qwt 6.1.0 source bundle with SVN version and it crashes.

To reproduce, download qwt-6.1.0.tar.bz2 from http://sourceforge.net/projects/qwt/files/ and then do svn checkout from:
svn checkout svn://svn.code.sf.net/p/qwt/code/branches/qwt-6.1

Extract the first archive and then use Kompare to compare the two directories.
For me, kompare shows the message box "The diff is malformed. Some lines could not be parsed and will not be displayed in the diff view." before crashing.

My setup:
KDE 4.11.3
Fedora 19, x86_64

Comment 21 Fedora End Of Life 2015-01-09 20:39:34 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 22 Fedora End Of Life 2015-02-17 19:20:46 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.