xmaxima "killing X11-server" Re: [Maxima] maxima and cmucl2002-08-13 don't fit

At 05:31 PM 10/18/02 -0500, James Amundson wrote:
>On Tue, 2002-10-15 at 13:50, Raymond Toy wrote:
>> >>>>> "jarausch" == jarausch  <jarausch@igpm.rwth-aachen.de> writes:
>
>>     jarausch> and doesn't kill my X11-server when finishing.
>> 
>> Really!  How is that possible?
>
>Ugh. There is a bug in xmaxima that causes it to appear to crash X11
>under the right circumstances. I say "appear to crash X11" because that
>isn't what happens at all. (I, too, had assumed it was crashing X11
>until I found the bug.) 

There used to be xn xmaxima bug that was killing the X11 server under Unix
because it was being called as "kill -SIGNAL" with no PID, and it depended
on the OS as to what that would do (presumably killing the parent of xmaxima).

The xmaxima code has been changed in 3 places to make sure that there is
a real PID to pass to kill, so it should not be killing the server anymore.
Note that crashing a server should produce a core dump under Unix, whereas
killing it will not. Was there a core dump being produced?

(Later on I'll get rid of the need for killing the local maxima subprocess,
but I wanted to leave if for after 5.9.0 final).

A note for those who noted long startup times for xmaxima. If this happens
again, can you tell me if you are connected to the Internet when this happens.
xmaxima.tcl itself if fast enough to startup, but it is using synchronous DNS
on the socket to the maxima subprocess. I can see Tcl taking its time to
timeout
on a DNS lookup of localhost (I'm not kidding). If this is the case there
are a
couple of ways around it, but the problem goes away when I fix the thing
above too.


Mike.