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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 9087 <at> debbugs.gnu.org
Subject: Re: bug#9087: Crash reading from minibuffer with icomplete-mode
Date: Mon, 18 Jul 2011 06:01:27 +0300

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Mon, 18 Jul 2011 04:07:50 +0200
> Cc: 9087 <at> debbugs.gnu.org
> 
> On Sun, Jul 17, 2011 at 05:08, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> > Wasn't the crash inside UNBLOCK_INPUT?
> 
> Wouldn't this
> 
>       --interrupt_input_blocked;
> 
> have triggered the interrupt_input_blocked watchpoint?

It should have.  But if the abort was not in UNBLOCK_INPUT, then I
don't understand the backtrace you posted: where else is the call to
`abort', if not inside UNBLOCK_INPUT?

Previous Next

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