26 Jun
2009
26 Jun
'09
3:39 p.m.
* Kelly McDonald [2009-06-26 02:03+0200] writes:
- Threads were not available
- the read-packet was getting interrupted by another swank event, it
would read the packet length from the stream, but the first event had not finished yet so it was reading random characters in the first event to determine the length of the next packet and it crashed in parse-integer 3) wait-for-event was being recalled before the event had completely decoded.
In theory, interrupts are queued during wait-for-event and processed at the next safe point. If the queue grows to large (3) we invoke the debugger immediately. In other words, the user needs to press C-c C-b three times in a row to get a partially decoded packet. At least that's the theory.
Helmut.