Eugen Dedu <Eugen.Dedu@pu-pm.univ-fcomte.fr> writes:
> I use powerpc and I experience the same behaviour with the new
> version. It's very annoying since I cannot see .ps files anymore (gv
> does not work anymore).
This looks like it's something to do with CID fonts:
select(5, [4], NULL, NULL, NULL) = 1 (in [4])
read(4, "\f\2\0\30\2@\0\1\0\0\0\0\3\6\3\352\0\0\5 \20\26E4\20\'"..., 32) = 32
write(4, "\2\30\0\4\2@\0\1\0\0\10\0\0\0\0\0005\30\0\4\2@\0\4\2@\0"..., 104) = 104
read(4, "\1\2\0\36\0\0\0\0\1\240\0\33\20\"\0\0\20\"\0\0\177\356"..., 32) = 32
read(3, "rentpagedevice dup length dict ."..., 4096) = 4096
read(3, "rrentsystemparams /GenericResour"..., 4096) = 4096
read(3, "h dup length dict copy\n dup /"..., 4096) = 4096
brk(0x10560000) = 0x10560000
read(3, "entdict /.cidfonttypes .undef\ncu"..., 4096) = 1559
read(3, "", 4096) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Though I can't be completely certain. It needs a gs with debugging
symbols to track down properly:
#0 0x100ae5f4 in ?? ()
#1 0x100ae614 in ?? ()
#2 0x100af17c in ?? ()
#3 0x1012562c in ?? ()
#4 0x10085600 in ?? ()
#5 0x10080c18 in ?? ()
#6 0x10081d5c in ?? ()
#7 0x100770fc in ?? ()
#8 0x10077834 in ?? ()
#9 0x1007a558 in ?? ()
#10 0x1000399c in ?? ()
#11 0x0effca34 in generic_start_main () from /lib/tls/libc.so.6
#12 0x0effcb84 in __libc_start_main () from /lib/tls/libc.so.6
#13 0x0effcb84 in __libc_start_main () from /lib/tls/libc.so.6
Previous frame inner to this frame (corrupt stack?)
Regards,
Roger
--
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
Attachment:
pgpyajGhlH76p.pgp
Description: PGP signature