abrt 1.0.0 detected a crash. How to reproduce ----- 1. Call dia from the command-line: dia --size='$width' --export=out.png in.dia 2. 3. Comment ----- Due to lame scripting, I accidentally called dia with a "--size=$width" parameter (rather than the $width getting substituted). It segfaulted on me, and does so consistently. Of course, the value for --size is not valid, but I'd expect a more graceful diagnostic. :-) Attached file: backtrace cmdline: dia --size= --export=SVC_KVM_Setup.png SVC_KVM_Setup.dia component: dia executable: /usr/bin/dia kernel: 2.6.31.9-174.fc12.x86_64 package: dia-1:0.97-3.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 380796 [details] File: backtrace
Interesting, i really cannot reproduce this on my end. Here is what i get [huzaifas@f12-test ~]$ dia --size= --export=test.png test.dia libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG test.dia --> test.png
Mmmh, it seems my initial bug report was indeed not correct: steven@cluestix-~ & dia --size=\$width --export=test.png test.dia libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG test.dia --> test.png But still, if I run the following: steven@cluestix-~ & dia --size= --export=test.png test.dia zsh: segmentation fault (core dumped) dia --size= --export=test.png test.dia It seems the "--size" does not like an empty argument: dia --size= --export=test.png test.dia dia --export=test.png --size= test.dia dia --export=test.png test.dia --size= All result in segfaults. The following doesn't crash, but gives an error message: dia --export=test.png test.dia --size Missing argument for --size<EOF> (The diagnostic is missing a newline at the end though.) The following just opens an empty "dia" window (i.e. it takes "test.dia" to be the argument to "--size" and apparently then ignores it). dia --export=test.png --size test.dia And the following does nothing: dia --size --export=test.png test.dia This seems to be some bug in the handling of options and arguments. It's not that urgent or bad, since everything works fine if you give it the proper arguments; it's just that the handling of exceptions/errors seems buggy. (Other than that, let me stress that dia is an excellent tool! :-))
I still cannot reproduce it [huzaifas@f12-test ~]$ dia --size= --export=test.png test.dia libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG test.dia --> test.png [huzaifas@f12-test ~]$ dia --export=test.png --size= test.dia libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG test.dia --> test.png [huzaifas@f12-test ~]$ dia --export=test.png test.dia --size= libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG test.dia --> test.png [huzaifas@f12-test ~]$ dia --export=test.png test.dia --size Missing argument for --size[huzaifas@f12-test ~]$ rpm -q dia dia-0.97-3.fc12.i686 More ever It seems you are using zsh and i could not reproduce issue with zsh too [huzaifas@f12-test]~% dia --export=test.png test.dia --size= libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG test.dia --> test.png
Mmmh, that's really weird. Are you running on 32 bits, by the way? I'm running on 64 bits; that's the only other possible difference between our setups that I can think of. $ uname -srimp Linux 2.6.31.9-174.fc12.x86_64 x86_64 x86_64 x86_64 Could it be a x86_64 specific bug? Cheers (and best wishes for 2010).
Yes i am on 32 bit. Also could you install debuginfo and get a traceback That way i can actually see what is going on. The current traceback isnt of much use as most of debuginfos are missing. Thanks.
ABRT is telling me there are 37 missing debuginfos, but it's not telling me which ones are missing :-( Is there any way I can figure out which 37 out of the 228 debuginfo packages I need?
Oh, and there's no "dia-debuginfo" package, I'm afraid.
How about debuginfo-install dia-0.97-3.f12.x86_64 as root?
That did it, although I had to issue "debuginfo-install dia" (without the version suffix). It's still complaining about 3 missing debuginfos though. Anyway, I'll attach the latest backtrace and core dump.
Created attachment 381517 [details] Backtrace #2
Created attachment 381518 [details] Coredump #2
Hi Steven, Can you also attach the file which is causing the crash? Perhaps its the file which is causing it. The file will help me to open a upstream bug, in case i cant figure out what is wrong.
Sure, I'll attach an example. It has three rectangles, nothing more. It seems that very trivial files (e.g. remove one rectangle, or resize it slightly, or move it a bit), don't trigger the crash, but give an error message instead: libpng error: Image width or height is zero in IHDR Error: Error occurred while writing PNG Still, something's off with the option parsing, it seems.
Created attachment 381770 [details] Simple test diagram that triggers the segfault Causes a crash when running on x86_64: dia --size= --export=test.png test3.dia Doesn't matter whether diagram file is compressed or not.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.