Red Hat Bugzilla – Bug 984325
[abrt] vbindiff-3.0-0.8.beta4.fc19: ConWindow::putAttribs: Process /usr/bin/vbindiff was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 11:09:17 EST
Description of problem:
I was comparing two files and pressed enter to jump to next (first) difference. The files were supposed to be same downloaded file, but one was interrupted in about two thirds and I want to check if one is really just truncated version of the other.
I could reproduce the crash:
1) take any file that is „longer than one screen“ (I took text file with GPL and it worked)
2) make a copy and truncate the file (so that one file is „prefix“ of the other)
3) run vbindiff on them (it seems it does not matter which file is first argument).
4) press enter (as to go to next difference)
(if crash did not happen at 4, then 5) press down arrow - for some files it was not necessary, for some it was and one could switch 4) and 5))
Version-Release number of selected component:
cmdline: vbindiff aaa.zip 'Stiahnut\xc3\xa9/Wasteland.zip'
runlevel: N 5
Thread no. 1 (3 frames)
#0 ConWindow::putAttribs at curses/ConWin.cpp:202
#1 FileDisplay::display at vbindiff.cpp:499
#2 handleCmd at vbindiff.cpp:1720
Created attachment 773440 [details]
Created attachment 773441 [details]
Created attachment 773442 [details]
Created attachment 773443 [details]
Created attachment 773444 [details]
Created attachment 773445 [details]
Created attachment 773446 [details]
Created attachment 773447 [details]
Created attachment 773448 [details]
Created attachment 773449 [details]
Here it crashes with different size files at startup, e.g. files created with the following can be used to reproduce the problem:
dd if=/dev/zero of=small.bin bs=1 count=0 seek=1
dd if=/dev/zero of=large.bin bs=1 count=0 seek=100
There is an upstream pull request taht is crash related, maybe it is the same issue:
Created attachment 842252 [details]
This patch fixes the bug for me.
Patch copied from https://github.com/nfllab/vbindiff/commit/931c9f35f934261de70b2d70fa171cec404d66af
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.