Re: gnus makes emacs lose response

[Chong Yidong]

>> leon <address@hidden> writes:
>>
>>> emacs still loses reponse and won't be able to restore to normal.
>>
>> And it doesn't respond to C-g ??
>
> No.
>
> (gdb) bt
> #0  0x00b79248 in ___newselect_nocancel () from /lib/libc.so.6
> #1  0x08194325 in select_wrapper (n=-514, rfd=0x0, wfd=0xbfcbe478, xfd=0x0, 
>     tmo=0xbfcbe5a8) at process.c:4188
> #2  0x081975e3 in wait_reading_process_output (time_limit=0, 
> microsecs=100000, 
>     read_kbd=0, do_display=0, wait_for_cell=137562313, wait_proc=0xac4b208, 
>     just_wait_proc=0) at process.c:4560

While Emacs is hung, could you go back to gdb, set a breakpoint at
interrupt_signal, and see what happens when you try to run C-g?  If
this drops you back into gdb at interrupt_signal, examine the values
of the following variables.

  b interrupt_signal
  c
   [Type C-g in Emacs -- this should drop back into gdb at interrupt_signal]
  p Qnil
  p Vquit_flag
  p immediate_quit
  p Vinhibit_quit
  p waiting_for_input
  p echoing

(If C-g doesn't drop you back into gdb at interrupt_signal, then it
probably is a kernel bug and there's nothing we can do about it).