[Bug: 21.4.12] xemacs: X Error of failed request: BadWindow(invalid Window parameter)

[Darryl Okahata]

Glynn Clements <glynn at gclements.plus.com> wrote:

> I've spent some time looking into similar errors in the past; I made
> some comments in:
> 
> http://list-archive.xemacs.org/xemacs-beta/200309/msg00056.html

     Here, you say:

	The window ID is taken from the SelectionRequest event, and
	doesn't look remotely valid; X window IDs tend to look like:
	0x00?000??, where the ?s are non-zero. So, at a glance, it looks
	like the problem may result from a bogus SelectionRequest event.

That's what I was wondering, because of the recursive calls to
execute_internal_event().  Recursive event processing makes me queasy.
I can't help but muse:

* As you say, one possibility is a synthetic SelectionRequest event with
  a bad window parameter (or some app is spewing bogus events).
  Perhaps, something inside XEmacs is generating it and putting it into
  the event queue.

* With recursive event handlers, could something be occurring
  out-of-order?  Maybe the handling is not really supposed to be
  recursive (with selections?)?

* Tony's problem (one of them, at least) seems to be occurring when he
  hits ^G.  Perhaps an event structure (possibly synthetic) is being
  corrupted or not being properly initialized because of the interrupt?

* Maybe someone (Tony?) could add some debugging printf()'s to display
  the window IDs of received SelectionRequest events?  This might help
  to narrow down the problem (bogus events vs corrupted events).

-- 
	Darryl Okahata
	darrylo at soco.agilent.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.