>>>> "MS" == Michael Sperber
<sperber(a)informatik.uni-tuebingen.de>:
John> the whole xemacs frame was blank and unresponsive - repeated C-g's did
John> nothing
MS> So just how exactly did you create the automated bug report?
er, uh, I had another xemacs dedicated to running VM - same build and
everything, so figured its version info and such would be enough, when
coupled with the backtrace
(incidently, that's why the attachment failed - generated the msg using
efs-report-bug and w/o thinking tried to just do M-x vm-mime-attach-file to
attach the file...)
John> eventually just killed the proc and got the backtrace in the shell window
John> I'd started xemacs in
MS> So it really seems as if there's a bug with the handling of process
MS> output, and with C-g. I've long suspected that, since I keep getting
MS> a thin trickle of non-reproducible or unanalyzable bug reports. (One
MS> recent VM bug report also suggested this.)
I have had to kill xemacs several times recently... this was just the first
time I've gotten anything at all useful... maybe I should start building
debug versions again...
-JT