On Fri, 1 Oct 2004 16:30:14 +0200 Dominik Vogt wrote about "Re: Notification:
incoming/1449":
I seem to have the same effect when doing like this:
I have an application panel'ed in FvwmButtons (namely psi)
I open the panel
Then, minimize the application with titlebar minimize button
Then, press the button on FvwmButtons to close panel
fvwm crashes, dumps core, and the stack trace looks the same:
== start ==
#0 0x0806a208 in HandleUnmapNotify (ea=0xbfbfe7b4) at events.c:3374
#1 0x0806a850 in dispatch_event (e=0xbfbfe7e0) at events.c:3616
#2 0x0806a91a in HandleEvents () at events.c:3661
#3 0x080951f2 in main (argc=2, argv=0xbfbfec30) at fvwm.c:2524
== stop ==
and those gdb commands you asked me to execute :-)
looks the same:
== start ==
(gdb) p te
$1 = (const XEvent *) 0x14
(gdb) p te->xunmap.window
Cannot access memory at address 0x28
(gdb) p dpy
$2 = (Display *) 0x811a000
(gdb) p ea
$3 = (const evh_args_t *) 0xbfbfe7b4
(gdb) p ea->exc
$4 = (const exec_context_t *) 0x8140180
(gdb) p ea->exc->x
$5 = {etrigger = 0x814019c, elast = 0x810ade0}
== stop ==
So I suppose this is a bug in fvwm code for handling unmapping windows in
general rather than exclusive firefox issue
--
wbr,
George 'Nephrite' Potapov
Inline Technologies
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
