Your message dated Sun, 5 Dec 2010 19:55:16 +0100
with message-id <[email protected]>
and subject line Re: Bug#489683: hugin-bin: hugin segfaults after disk filled up
has caused the Debian Bug report #489683,
regarding hugin-bin: hugin segfaults after disk filled up
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
489683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489683
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: hugin-bin
Version: 0.6.1-1.3
Severity: important
Hi,
If hugin fills up the disk when writing the output files, it
reproducibly crashes with a segfault. Since hugin does not provide a
-dbg package and I'm currently short of time to generate one myself, I
cannot provide a backtrace or any other additional useful information.
You should be able to easily reproduce it by writing to a small (e.g.
loop-back mounted) device though.
Cheers,
Sebastian
--
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 2010.4.0+dfsg~beta2-1
On 2008-07-07 Sebastian Harl <[email protected]> wrote:
> Package: hugin-bin
> Version: 0.6.1-1.3
> Severity: important
> Hi,
> If hugin fills up the disk when writing the output files, it
> reproducibly crashes with a segfault. Since hugin does not provide a
> -dbg package and I'm currently short of time to generate one myself, I
> cannot provide a backtrace or any other additional useful information.
> You should be able to easily reproduce it by writing to a small (e.g.
> loop-back mounted) device though.
Hello,
I have finally taken the (small) effort to try to reproduce this. Current
hugin (available in experimental) does not crash.
The stitch fails of course, and shows an error message like this one:
------------------------------------
nona -z PACKBITS -r ldr -m TIFF_m -o p1000717-p1000722 -i 1
/mnt/ametz/huginpto_q7L3GD
TIFFAppendToStrip: Write error at scanline 602.
TIFFAppendToStrip: Write error at scanline 602.
TIFFAppendToStrip: Write error at scanline 516.
TIFFAppendToStrip: Write error at scanline 516.
ContractViolation:
Postcondition violation!
exportImage(): Unable to write TIFF data.
(/tmp/HUGIN/hugin-2010.4.0/src/foreign/vigra/vigra_impex/tiff.cxx:749)
TIFFAppendToStrip: Write error at scanline 516.
caught exception:
Postcondition violation!
exportImage(): Unable to write TIFF data.
(/tmp/HUGIN/hugin-2010.4.0/src/foreign/vigra/vigra_impex/tiff.cxx:749)
make: *** [p1000717-p10007220001.tif] Error 1
------------------------------------
The error message could probably be a little bit nicer, but that is
different kind of bug than crash&data-loss. Which is why I am closing
this one.
There is already an upstream report about handling the error in a more
user friendly / obvious way.
See https://bugs.launchpad.net/hugin/+bug/679941
cu andreas
--- End Message ---
_______________________________________________
Pkg-phototools-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-phototools-devel
