emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnus makes emacs lose response


From: Kim F. Storm
Subject: Re: gnus makes emacs lose response
Date: Sun, 10 Sep 2006 00:33:24 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

On Thu, 09/07/2006 15:48 +0100, Kim F. Storm wrote:

> From: Chong Yidong <address@hidden>
> Subject: Re: gnus makes emacs lose response
> Newsgroups: gmane.emacs.devel
> Cc: address@hidden, "Kim F. Storm" <address@hidden>
> Date: Thu Sep  7 15:37:23 2006 +0100
>
>>> 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).
> ----------

Here is the log. C-g can return to gdb.


GNU gdb Red Hat Linux (6.5-7.fc6rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db 
library "/lib/libthread_db.so.1".

DISPLAY = :0.0
TERM = xterm
Breakpoint 1 at 0x80fe1d6: file emacs.c, line 464.
Breakpoint 2 at 0x8116866: file sysdep.c, line 1395.
(gdb) r
Starting program: /home/tmp/emacs/src/emacs -geometry 80x40+0+0
[Thread debugging using libthread_db enabled]
[New Thread -1208244544 (LWP 10921)]
[Switching to Thread -1208244544 (LWP 10921)]
Breakpoint 3 at 0x80d2b2c: file xterm.c, line 8039.

Program received signal SIGTSTP, Stopped (user).
0x00908402 in __kernel_vsyscall ()
(gdb) b interrupt_signal
Breakpoint 4 at 0x8102435: file keyboard.c, line 10389.
(gdb) c
Continuing.

Breakpoint 4, interrupt_signal (signalnum=0) at keyboard.c:10389
10389     int old_errno = errno;
(gdb) p Qnil
$1 = 137562313
(gdb) p Vquit_flag
$2 = 137562313
(gdb) p immediate_quit
$3 = 0
(gdb) p Vinhibit_quit
$4 = 137562361
(gdb)  p waiting_for_input
$5 = 0
(gdb)  p echoing
$6 = 0
(gdb) 


regards,
-- 
Leon

-- 
Kim F. Storm <address@hidden> http://www.cua.dk





reply via email to

[Prev in Thread] Current Thread [Next in Thread]