[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Texmacs-dev] Problem with Ghostscript
From: |
Joris van der Hoeven |
Subject: |
Re: [Texmacs-dev] Problem with Ghostscript |
Date: |
Fri, 2 May 2003 22:01:47 +0200 (CEST) |
Hi Michele,
Thanks for your detailed feedback.
I am a bit confused by two of your experiments.
In the first case with tm_gnu1.ps and tm_gnu2.ps,
you obtain the following:
> I obtain:
>
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.26
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1016 - Ss p2 0:00.23
> -tcsh (tcsh)
> 501 4398 4376 0 14 0 20168 8980 - R+ p2 0:05.65
> texmacs.bin
>
> texmacs is runnable again. Normal it's loading the fonts and so on.
>
> 6 - A few second later, I obtain:
>
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.26
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1016 - Ss p2 0:00.23
> -tcsh (tcsh)
> 501 4398 4376 0 26 0 20816 9328 - S+ p2 0:05.90
> texmacs.bin
> 501 4656 4398 0 27 0 14532 3460 - S+ p2 0:00.22
> (gs)
>
> gs have been launched by texmacs, both are sleeping and in the
> foreground process group,. gs is trying to process tm_gnu1.ps. Here I
> suspect that texmacs does not handle gs with signal and timer, in order
> to kill gs as apparently it hangs. So I cannot say it's normal, but it
> reflects the situation: texmacs is waiting for gs to terminate and gs
> cannot send its terminating signal to texmacs, due possibly to a signal
> that is not caught by texmacs (just my guess, I have not browsed the
> code).
>
> 7 - I send a ctrl-C in xterm.
>
> I obtain:
>
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.26
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1016 - Ss p2 0:00.23
> -tcsh (tcsh)
> 501 4398 4376 0 31 0 20816 9336 - S+ p2 0:06.04
> texmacs.bin
> 501 4661 4398 0 31 0 14532 3460 - S+ p2 0:00.23
> (gs)
>
> Idem as above with tm_gnu2.ps
>
> 8 - I send another ctrl-C in xterm
>
> I obtain:
>
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.26
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1016 - Ss p2 0:00.23
> -tcsh (tcsh)
> 501 4398 4376 0 31 0 20552 9212 - R+ p2 0:06.15
> texmacs.bin
>
> Ok, gs is killed, texmacs is runnable again.
In the second case, a 3.2Mb ps file, you obtain:
> > (In order to check this, you may create a postscript
> > file which needs a long to be displayed and carefully
> > track what happens when opening it from TeXmacs).
> I've tried it with a 3.2 Mo ps file, running from gs
>
> I obtain:
>
> 1 - first
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.36
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1024 - Ss p2 0:00.29
> -tcsh (tcsh)
> 501 4714 4376 0 14 0 7272 3512 - R+ p2 0:02.29
> gs balloon-2.en.ps
>
> 2 - thereafter
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.37
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1024 - Ss p2 0:00.29
> -tcsh (tcsh)
> 501 4714 4376 0 31 0 7196 3436 - S+ p2 0:02.35
> gs balloon-2.en.ps
>
> When running inside texmacs (insert an image):
>
> 1 -
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.37
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1024 - Ss p2 0:00.31
> -tcsh (tcsh)
> 501 4719 4376 0 28 0 27088 14140 - R+ p2 0:09.92
> texmacs.bin
>
> 2 -
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.39
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1024 - Ss p2 0:00.31
> -tcsh (tcsh)
> 501 4719 4376 0 31 0 27088 14188 - S+ p2 0:15.31
> texmacs.bin
> 501 4911 4719 0 0 0 14628 3560 - R+ p2 0:00.61
> (gs)
>
> 3-
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.39
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1024 - Ss p2 0:00.31
> -tcsh (tcsh)
> 501 4719 4376 0 23 0 27088 14188 - R+ p2 0:15.45
> texmacs.bin
>
> 4-
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME
> COMMAND
> 501 4285 4284 0 31 0 6176 1020 - S std 0:00.42
> -tcsh (tcsh)
> 501 4376 4375 0 31 0 6176 1024 - Ss p2 0:00.31
> -tcsh (tcsh)
> 501 4719 4376 0 31 0 22988 10844 - S+ p2 0:16.10
> texmacs.bin
Now in the last case, the gs process has automagically disappeared,
although TeXmacs did not return to R+. Is that normal,
or did you press Ctrl-C?
Re: [Texmacs-dev] Problem with Ghostscript, Karl M. Hegbloom, 2003/05/02
Re: [Texmacs-dev] Problem with Ghostscript, Ralf Treinen, 2003/05/02