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

Previous Next

Full log

View this message in rfc822 format

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

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Fri, 15 Jul 2011 17:12:41 +0200
> Cc: 9087 <at> debbugs.gnu.org
> 
> On Fri, Jul 15, 2011 at 14:29, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> > Could you perhaps repeat the recipe after setting a watchpoint on the
> > variable interrupt_input_blocked, with commands like this:
> >
> >  p interrupt_input_blocked
> >  bt 5
> >  continue
> 
> I'm sorry, I think you'll have to downgrade your expectations about my
> GDB-foo and explain things more slowly and with easy words ;-)

Compliance!

 whatever> gdb ./oo/i386/emacs.exe
 (gdb) watch interrupt_input_blocked
 (gdb) commands
  >p interrupt_input_blocked
  >bt 5
  >continue
  >end
 (gdb) run ....

Now each time interrupt_input_blocked will change its value, GDB will
kick in, perform the named "commands", and let Emacs continue.  Do
whatever you need to reproduce the crash, then look at what GDB
printed, and see if the increments/decrements of this variable come in
pairs, as they should, or not.  Note that they could be nested, so
just 2 increments in a row are okay if there are 2 decrements in a row
after that.

See the definitions of BLOCK_INPUT and UNBLOCK_INPUT, for more
insight.

Previous Next

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