[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: ZVONA at MIT-AI
- Subject: QSEND damage
- From: David L. Andre <DLA at MIT-AI>
- Date: Sun ,10 Jan 82 02:39:00 EDT
- Cc: BUG-LISPM at MIT-AI, CSTACY at MIT-AI
Date: Saturday, 9 January 1982, 14:42-EST
From: David Chapman <Zvona at MIT-AI>
I did a qsend to someone who apparently was rejecting.
Pop-up-receive-qsend tried to take an array leader of
a null string without a leader.
I did a qsend to someone whose qsend process had lost. It (tried to) tell me
that he was rejecting; not the same thing at all.
I'm not sure if I fixed your bugs, but 78.37 fixed all of the damage
associated with QSEND that I could find. The QSEND-GAGGED hack now
rejects the connection, with the reason being what the message was
previously. When the QSEND is from another lisp machine, the sender
will be given that reason and asked whether to mail instead.