Am Wednesday 24 September 2008 schrieb cspiel:
> 
> Michael -
> 
> Michael Galloway wrote:
> > is the segfault with enblend cvs resolved?
> 
> At least I cannot reproduce it with the latest CVS version
> on my machine
>     $ uname -a
>     Linux beliskner 2.4.36 #3 SMP Thu Feb 14 15:51:55 CET 2008 i686
> GNU/Linux
> and my compiler
>     $ gcc --version
>     gcc (GCC) 4.3.2
> However, this doesn't prove the bug went away.

On my machine it is 
Linux dell64 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC x86_64 x86_64 
x86_64 GNU/Linux

and here enblend still segfaults.

> Could you please give it a spin?  If you run into a segfault
> a backtrace would be helpful.

I have a backtrace, but not very helpfull.

....
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /usr/lib64/libXau.so.6...done.
Loaded symbols for /usr/lib64/libXau.so.6
Core was generated by `enblend -o xb0000.tif -v -m 400 -l 20 -w -a --fine-mask 
--optimize xa0005.tif x'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000004f676e in enblend::maskBounds<vigra::CachedFileImage<unsigned 
char> > ()
(gdb) bt
#0  0x00000000004f676e in enblend::maskBounds<vigra::CachedFileImage<unsigned 
char> > ()
#1  0x000000000063a17e in enblend::enblendMain<vigra::RGBValue<unsigned char, 
0u, 1u, 2u> > ()
#2  0x0000000000408d42 in main ()
(gdb)

> Cheers,
>     Chris

        Kornel
-- 
Kornel Benko
[EMAIL PROTECTED]

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to