[9fans] ps2pdf

[9fans] ps2pdf

[givanes]

Hi there,

I tried to convert ps to pdf :

plan9% troff lettre_de_motivation.txt > lettre_de_motivation.ps
plan9% ps2pdf lettre_de_motivation.ps lettre_de_motivation.pdf
gs 3658: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55

plan9% man -t upasfs > upasfs.ps
plan9% ps2pdf upasfs.ps upasfs.pdf
gs 3721: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55

Why so ?

Gab

Re: [9fans] ps2pdf

[jmk]

GIGO.

Troff does not produce PostScript output, so you are passing
garbage in to ps2pdf. However, on my system gs does not suicide but
presents a useful error:

ethel% man -t upasfs > upasfs.ps
ethel% ps2pdf upasfs.ps upasfs.pdf
Error: /undefined in x
Operand stack:

Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1122/1686(ro)(G)--   --dict:0/20(G)--   --dict:70/200(L)--
Current allocation mode is local
Current file position is 2
AFPL Ghostscript 8.53: Unrecoverable error, exit code 1
ethel% B /tmp/upasfs.ps
ethel% 

so you have some other problem as well, perhaps out of date binaries.

Usually, when presented with something like

	gs 3721: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55

running a couple of simple acid commands on the process is a useful
first step in figuring out what is wrong, either for yourself or to
pass on to others you ask for help. E.g.

	acid 3721
			<- some output here
	stk()
			<- some output here
	regs()
			<- some output here
	asm(*PC)
			<- some output here

and in this case, because there was an FP error

	fpr()
			<- some output here
	asm(0xd525a)
			<- some output here

I leave it up to you to read the manual for the description
of those commands and how to interpret the output.

--jim

On Tue May  2 10:09:40 EDT 2006, givanes@gmail.com wrote:
> Hi there,
> 
> I tried to convert ps to pdf :
> 
> plan9% troff lettre_de_motivation.txt > lettre_de_motivation.ps
> plan9% ps2pdf lettre_de_motivation.ps lettre_de_motivation.pdf
> gs 3658: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55
> 
> plan9% man -t upasfs > upasfs.ps
> plan9% ps2pdf upasfs.ps upasfs.pdf
> gs 3721: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55
> 
> Why so ?
> 
> Gab

Re: [9fans] ps2pdf

[givanes]

[-- Attachment #1: Type: text/plain, Size: 106 bytes --]

That's it. I was using the 8.13's binary.
But at this point i've got the same error that you have.

Gab

[-- Attachment #2: Type: message/rfc822, Size: 5491 bytes --]

From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ps2pdf
Date: Tue, 2 May 2006 11:56:50 -0400
Message-ID: <8c4fb22c7c9c46f9be239add1fd17e01@plan9.bell-labs.com>

GIGO.

Troff does not produce PostScript output, so you are passing
garbage in to ps2pdf. However, on my system gs does not suicide but
presents a useful error:

ethel% man -t upasfs > upasfs.ps
ethel% ps2pdf upasfs.ps upasfs.pdf
Error: /undefined in x
Operand stack:

Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1122/1686(ro)(G)--   --dict:0/20(G)--   --dict:70/200(L)--
Current allocation mode is local
Current file position is 2
AFPL Ghostscript 8.53: Unrecoverable error, exit code 1
ethel% B /tmp/upasfs.ps
ethel% 

so you have some other problem as well, perhaps out of date binaries.

Usually, when presented with something like

	gs 3721: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55

running a couple of simple acid commands on the process is a useful
first step in figuring out what is wrong, either for yourself or to
pass on to others you ask for help. E.g.

	acid 3721
			<- some output here
	stk()
			<- some output here
	regs()
			<- some output here
	asm(*PC)
			<- some output here

and in this case, because there was an FP error

	fpr()
			<- some output here
	asm(0xd525a)
			<- some output here

I leave it up to you to read the manual for the description
of those commands and how to interpret the output.

--jim

On Tue May  2 10:09:40 EDT 2006, givanes@gmail.com wrote:
> Hi there,
> 
> I tried to convert ps to pdf :
> 
> plan9% troff lettre_de_motivation.txt > lettre_de_motivation.ps
> plan9% ps2pdf lettre_de_motivation.ps lettre_de_motivation.pdf
> gs 3658: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55
> 
> plan9% man -t upasfs > upasfs.ps
> plan9% ps2pdf upasfs.ps upasfs.pdf
> gs 3721: suicide: sys: fp: invalid operation fppc=0xd525a status=0xb8a1 pc=0x000d4f55
> 
> Why so ?
> 
> Gab