I'm getting a similar segmentation fault in enblend with the
current fc8.x86_64 package (enblend-3.1-0.5.20080723cvs.fc8)
--
Markku Kolkka
markku...@iki.fi
>I'm getting a similar segmentation fault in enblend with the
>current fc8.x86_64 package (enblend-3.1-0.5.20080723cvs.fc8)
Yes current enblend CVS is broken (at least on x86_64 as the reports
I've seen are all on x86_64).
Regarding the fedora enblend package, I've removed the broken RPM
from the repository. Until I get a replacement set released, you
have to downgrade manually to the previous 20080714cvs RPM - The
easiest way to do this is to uninstall hugin/enblend and reinstall.
--
Bruno
32-bit, unless it's actually x86_64, which would mean 64-bit.
> Ubuntu's latest enblend package has version 3.0 and is therefore too
> old.
>
> How can I build the last stable enblend revision ?
[1] might still help (we added a workaround for the --compression
feature, as documented in README.Debian, which you'll find in
/usr/share/doc/hugin, or online[1]).
1. http://packages.debian.org/sid/hugin
2. http://lists.alioth.debian.org/pipermail/pkg-phototools-devel/2008-July/000358.html
Feedback is very welcome.
Mraw,
KiBi.
Just follow the enblend compilation instructions except download
the last known 'good' CVS snapshot instead of the current 'head':
cvs -d:pserver:anon...@enblend.cvs.sourceforge.net:/cvsroot/enblend login
cvs -z3 -d:pserver:anon...@enblend.cvs.sourceforge.net:/cvsroot/enblend co -D '2008-07-18 21:00:00' -P enblend
--
Bruno
I wasn't sure whether you were talking about the latest enblend release,
or the latest enblend CVS snapshot known to be working. In the former
case, I meant to point that enblend 3.0 is packaged, but I provided you
with an hugin link, sorry.
> I tried this, but get the same segmentation fault as in enblend of
> july 25.
>
> I guess enblend is also broken for normal 32bit systems (system
> type... i686-pc-linux-gnu) as I can't find any 64 bit switches in my
> configuration.
Maybe we could try a debug build (with -g, without stripping), and
provide a backtrace, so that people can compare them? Maybe they are
different issues after all.
> The only 64 bit compiler switch is -D_FILE_OFFSET_BITS=64 which does
> not seem to be a cpu specification.
Yep, that is LFS (Large File Support), needed to open large files.
Mraw,
KiBi.
I tried. But then enblend did not crash.
Compile with "-g3" ==> no crash
Compile with "-g -O" ==> crash.
Debugging the second leads you deep into templates of "mask.h", but I was unable to see the cause.
One cannot step to the error case, because it takes ages, so I had to run it and wait for crash.
But then the stack does not look correct.
> > The only 64 bit compiler switch is -D_FILE_OFFSET_BITS=64 which does
> > not seem to be a cpu specification.
> Yep, that is LFS (Large File Support), needed to open large files.
>
> Mraw,
> KiBi.
>
Kornel
--
Kornel Benko
Kornel...@berlin.de