GNU bug report logs - #9310
BadWindow error with quail guidance frame

Previous Next

Full log

View this message in rfc822 format

From: "Jan D." <jan.h.d <at> swipnet.se>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 9310 <at> debbugs.gnu.org
Subject: bug#9310: BadWindow error with quail guidance frame
Date: Tue, 23 Aug 2011 08:17:52 +0200

Stefan Monnier skrev 2011-08-23 04:23:
>>>>> emacs -Q --eval "(setq default-frame-alist '((minibuffer . nil)))" --eval
>>>>> (quail-define-package "Agda" "UTF-8" "A" t)'
>>>>> C-u C-\ agda RET
>>>>> M-%
>>>>> and I get the appended backtrace.  As the input method name explains,
>>>>> I bump into this problem when I use Agda (i.e. pretty often these days).
>>>> Is it possible that the frame switched to (0x8c793d8 at #13) is deleted?
>>> AFAIK no frame is deleted in the above scenario, and the frame's
>>> `terminal' field is not NULL (if that's what you were asking).
>>> 0x8c793d8 is the minibuffer-only frame.
>>> IIUC your question, you can't reproduce it on your end?
>> No I can not.
>
> Can someone help me figure out how to debug this (my X11 programming is
> part rusty part nonexistent)?
>

Basically set synchronized and break in the error function.  Then go up 
the call stack to find the frame the window belongs to, or see if it is 
some uninitialized value.

	Jan D.

Previous Next

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