Re: non-critical problem...

[Ethan A M. <merritt@u.washington.edu>]

On Tuesday 13 April 2004 08:55 pm, Daniel J Sebald wrote:
> It can't get back to the terminal.  It is stuck at "gnuplot>".
>  Actually, the sequence is stranger than I originally thought.  After
> the Exec failure, the screen will respond to keyboard hits but not
> process anything, i.e.,
>
> Then from there, CNTRL-C will bring back "gnuplot>", but the terminal is
> then unresponsive to any keyboard hits... except for a CNTRL-C which
> then displays another "gnuplot>" prompt as though CR was hit.

Right.  It's stuck in term->waitforinput().

> I get two process IDs showing up attributed to "gnuplot"
>
>  1081 pts/4    00:00:00 gnuplot
>  1082 pts/4    00:00:00 gnuplot <defunct>

gnuplot forks inside x11.trm, and the daughter process tries to
execv("gnuplot_x11").  If the execv() had succeeded, that daughter
process would have become "gnuplot_x11". But it failed, so it's still
reported as being "gnuplot".

> >Could be.  Ethan, I guess this one's in your ballbark --- I'm almost
> >willing to bet it's caused by the mouse or font feedback stuff, so
> >please see if you can do something about it.

I see it.  If the piped closes unexpectly, one of the lock flags
needs to be reset so that the waitforinput() loop doesn't continue
forever.  Fixed in cvs.

	Ethan  


-- 
Ethan A Merritt
Department of Biochemistry & Biomolecular Structure Center
University of Washington, Seattle