bug report

[Stephen J. Turnbull]

Koni writes:

 > An inferior gdb buffer can cause xemacs to hang if the processing
 > being debugged is interrupted from xemacs by C-c C-c while it is
 > writing a lot of output to stdout/stderr which is appearing in the
 > buffer. No xemacs commands will work if this happenes, to regain
 > control of xemacs, one must kill gdb from a shell somewhere
 > else. Killing gdb allows xemacs to recover and one can then kill
 > then buffer as normal.

I'm sorry for the long delay in responding.  Is this an immediate
problem in getting work done, or can you work around by killing gdb as
described above?

I forwarded your post to the developer most likely to be able to
resolve the issue, but he hasn't responded.  This kind of issue is
very difficult to localize, let alone fix.  I'm sorry, but we're
almost forced to let it wait until one of the experts can look at it.

Steve