Description of problem: comparing a pair of large files. used the keyboard commands t, b, end etc, maybe faster than the app could process them. Version-Release number of selected component: vbindiff-3.0-0.9.beta4.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: vbindiff 'How I Met Your Mother.2014_04_28.b_1_1.mpg' 'How I Met Your Mother.2014_04_28.b_1_2.mpg' crash_function: ConWindow::putAttribs executable: /usr/bin/vbindiff kernel: 3.13.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: 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:1719 Potential duplicate: bug 984325
Created attachment 892221 [details] File: backtrace
Created attachment 892222 [details] File: cgroup
Created attachment 892223 [details] File: core_backtrace
Created attachment 892224 [details] File: dso_list
Created attachment 892225 [details] File: environ
Created attachment 892226 [details] File: exploitable
Created attachment 892227 [details] File: limits
Created attachment 892228 [details] File: maps
Created attachment 892229 [details] File: open_fds
Created attachment 892230 [details] File: proc_pid_status
Created attachment 892231 [details] File: var_log_messages
Another user experienced a similar problem: Comparing 2 similar mp3 files. (ffmpeg has re-written the headers, but with acodec:copy so body(music) is the same. T move top,u/d/l/r B move bottom, u/d/l/r (this aligned the binary contents which are shifted after the mp4 headers (different length), but otherwise identical (mp3 content). page down a few times. end. Top file showing position= 2480, bottom=25D6 I think this might have tried to seek in the shorter file past it's length... just guessing. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: vbindiff alex_lloyd.10.lucky_star.mp3 alex_lloyd.10.lucky_starb.mp3 crash_function: ConWindow::putAttribs executable: /usr/bin/vbindiff kernel: 3.14.6-200.fc20.x86_64 package: vbindiff-3.0-0.9.beta4.fc20 reason: vbindiff killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Comparing binary files: 1. vbindiff DIR1/FILE1 DIR2/FILE2 2. Enter several times to get to the end 3. Scrolling few lines up 4. T to get to the top 5. Enter reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: vbindiff 32/Hamlib.pyc 64/Hamlib.pyc crash_function: ConWindow::putAttribs executable: /usr/bin/vbindiff kernel: 3.14.5-200.mst.fc20.x86_64 package: vbindiff-3.0-0.9.beta4.fc20 reason: vbindiff killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Both files were the same size.
Created attachment 910765 [details] File used in reproducer Reproducer: $ vbindiff Hamlib.pyc Hamlib.pyc 1. T 2. Enter 3. T 4. Page Up
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
vbindiff-3.0-0.13.beta4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/vbindiff-3.0-0.13.beta4.fc21
vbindiff-3.0-0.13.beta4.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/vbindiff-3.0-0.13.beta4.fc22
Package vbindiff-3.0-0.13.beta4.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing vbindiff-3.0-0.13.beta4.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9265/vbindiff-3.0-0.13.beta4.fc22 then log in and leave karma (feedback).
I've left positive karma on the above URL.
vbindiff-3.0-0.13.beta4.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
vbindiff-3.0-0.13.beta4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.