On 09/02/10 12:27, Eric Adriaans | Dsens wrote:
Hey Joseph,
I think all dependencies are ok now, though I'm a bit confused about what
the 'linux-gate.so.1' dependency is, since by the looks of it, it doesn't
point anywhere.
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)
What I noticed now though, is that the output generated by my php-script,
doesn't show the error which is generated by pdf2swf. When I execute pdf2swf
in the shell, it shows:
[r...@baopass 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
I checked the mailinglist, and I found one similar problem. I'll reply to
that thread too :)
Eric
Now, we need to find out what is causing the SIGFPE. I usually use gdb
to debug programs.
I will show the simplest possible way to debug pdf2swf, if you want more
details, please consult the documentation:
http://sourceware.org/gdb/current/onlinedocs/gdb/
1. Start a gdb session:
gdb /usr/local/bin/pdf2swf [this needs to be the full path to your
pdf2swf executable]
2. then at the (gdb) prompt issue:
run <filename>.pdf -o <output>.swf
Can you copy and paste the output. (Please do not include the "(no
debugging symbols found)" messages).
3. use the "quit" command to exit the session
