GNU bug report logs - #9087
Crash reading from minibuffer with icomplete-mode

Previous Next

Full log

Message #173 received at 9087 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: claudio.bley <at> gmail.com, lekktu <at> gmail.com, 9087 <at> debbugs.gnu.org,
	monnier <at> iro.umontreal.ca, jasonr <at> gnu.org
Subject: Re: bug#9087: Crash reading from minibuffer with icomplete-mode
Date: Sat, 07 Jan 2012 17:27:45 +0100

> This call to QUIT is the problem, because this code runs in a
> different thread than the main Lisp thread, the one that set up the
> setjmp point to which we longjmp when we throw to top level.  So it
> unwinds the wrong stack.

Thanks.  I'm beginning to understand.  Is post_character_message the
only potential source of this problem or are there others as well?

> By contrast, C-g does not call signal_user_input to be called, see
> above.  So it avoids this fate.

Naively asked: Could we avoid the problem if on normal input we did not
call signal_user_input but did something similar to C-g handling?

martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.