Re: [Swftools-common] Floating point exception in pdf2swf on 64bit linux

[Chris Pugh]

On 9 February 2010 12:30, Eric Adriaans | Develicious
<address@hidden> wrote:
> Hi Matthias and Michael,
>
>
>
> I’m now experiencing the same problem, our CentOS 5.4 server generated the
> same Floating point exception:
>
>
>
> address@hidden eric]# pdf2swf -vv -T9 LB5a_Compl_FC.pdf -o
> /eric/pdf2swftest/LB5a_Compl_FC.swf
>
> VERBOSE setting parameter flashversion to "9"
>
> VERBOSE Generating info structure for page 1
>
> VERBOSE Generating info structure for page 2
>
> Floating point exception
>
>
>
> Did you figure out what was the problem in the end? I’ve checked the
> dependencies, maybe there’s something wrong there?
>
>
>
> ldd /usr/local/bin/pdf2swf
>
>         linux-gate.so.1 =>  (0x00beb000)
>
>         libmp3lame.so.0 => /usr/lib/libmp3lame.so.0 (0x00cbf000)
>
>         libungif.so.4 => /usr/lib/libungif.so.4 (0x00dbf000)
>
>         libjpeg.so.62 => /usr/local/lib/libjpeg.so.62 (0x00c01000)
>
>         libz.so.1 => /usr/local/lib/libz.so.1 (0x00755000)
>
>         libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x006cd000)
>
>         libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00991000)
>
>         libm.so.6 => /lib/libm.so.6 (0x00519000)
>
>         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0079d000)
>
>         libc.so.6 => /lib/libc.so.6 (0x003b1000)
>
>         libgif.so.4 => /usr/lib/libgif.so.4 (0x002bd000)
>
>         /lib/ld-linux.so.2 (0x0038e000)
>
>         libX11.so.6 => /usr/lib/libX11.so.6 (0x00110000)
>
>         libXau.so.6 => /usr/lib/libXau.so.6 (0x003ac000)
>
>         libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00213000)
>
>         libdl.so.2 => /lib/libdl.so.2 (0x004f9000)
>
>
>
> Thanx,
>
>
>
> Eric

Eric,

I think Joseph has mentioned gdb?

  http://www.gnu.org/software/gdb/

Do you have it installed?  It should locate exactly where the
fall-over is taking place, that is
if you are into tinkering.

I could take a wild stab in the dark.. it is quite possible that
SWFTools has partly compiled itself against a 32bit library somewhere
along the line, when it should have actually used a 64bit version?

Thought you had reported this as working?  What did you change?  ;o)

Regards,


Chris.