On Thu, 30 Sep 2004 18:12:57 +0200 Dominik Vogt wrote about "Re: Notification: incoming/1449":
[skip] > Can you please fetch a stack trace and post it to the fvwm-workers > list? > > $ gdb fvwm core > (gdb) where I managed to get the stack trace for recent fvwm crash, here it is: == start == Core was generated by `fvwm'. Program terminated with signal 11, Segmentation fault. #0 0x0806a208 in HandleUnmapNotify (ea=0xbfbfe384) at events.c:3374 3374 XUnmapWindow(dpy, te->xunmap.window); #0 0x0806a208 in HandleUnmapNotify (ea=0xbfbfe384) at events.c:3374 #1 0x0806a850 in dispatch_event (e=0xbfbfe3b0) at events.c:3616 #2 0x0806a91a in HandleEvents () at events.c:3661 #3 0x080951f2 in main (argc=2, argv=0xbfbfe80c) at fvwm.c:2524 == end == Everything else the same: it was caused by firefox file/quit menu -- 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]
