23 Aug
2017
23 Aug
'17
9:36 p.m.
On Wed, Aug 23, 2017 at 2:49 PM, PR <polos.ruetz@gmail.com> wrote:
So, it basically seems a network communication problem.
Looking at the event log doesn't seem to yield much of a clue. Perhaps you can try setting swank::*debug-on-swank-protocol-error* to t. If that doesn't help, you could try to place a break at the start of swank::close-connection% to see what's triggering it. HTH, Luís