Author ajb
Recipients ajb, jafo
Date 2007-09-18.15:40:36
SpamBayes Score 0.0369527
Marked as misclassified No
Message-id <>
The exception would count as a warning if it wasn't EGAIN. One expects
to catch EGAIN and try again.

The current situation is unfortunate because it *nearly* works. My
scenario is: I'm driving GDB/MI via popen2.Popen3 ( gdbCommand, False,1).
It works for most GDB commands, but sometimes GDB returns a huge line
and I get EGAIN in the middle. (For my purposes, I've worked round it,
by avoiding the command which generates a long line)
Date User Action Args
2007-09-18 15:40:36ajbsetspambayes_score: 0.0369527 -> 0.0369527
recipients: + ajb, jafo
2007-09-18 15:40:36ajbsetspambayes_score: 0.0369527 -> 0.0369527
messageid: <>
2007-09-18 15:40:36ajblinkissue1175 messages
2007-09-18 15:40:36ajbcreate