[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crashes when pressing ^G in minibuffer
From: |
Eli Zaretskii |
Subject: |
Re: Crashes when pressing ^G in minibuffer |
Date: |
Fri, 26 Oct 2001 16:58:24 +0200 |
> From: Alf-Ivar Holm <alfh@ifi.uio.no>
> Date: Fri, 26 Oct 2001 15:47:31 +0200 (MET DST)
>
> I've not managed to reproduce this error in an empty emacs (-q), but
> I've got this crash twice while running gnus (and lots of other setup
> stuff loaded from a lot of different files) and both times while I was
> editing the prompt to "M-x man". The initial message and backtrace
> from gdb (Note: emacs21 was started with "run -nw" in gdb):
>
> Program received signal SIGINT, Interrupt.
> 0xfef9629c in _poll () from /usr/lib/libc.so.1
> (gdb) backtrace
> #0 0xfef9629c in _poll () from /usr/lib/libc.so.1
> #1 0xfef4e86c in select () from /usr/lib/libc.so.1
> #2 0x191afc in wait_reading_process_input ()
> #3 0x4cb54 in sit_for ()
> #4 0x4cc68 in Fsit_for ()
I'm confused: this isn't a crash, this is SIGINT. SIGINT is the
signal produced by C-g in Emacs. And since you pressed C-g, it's
quite expected to get a SIGINT.
Is it possible that this is a result of Gnus running some async code
behind your back (off an idle timer), and thus your C-g interrupts
that Gnus code?