Dominik Vogt wrote:
On Wed, Jan 30, 2008 at 05:55:55PM +0100, Philipp Kolmann wrote:
Hi,
I have had several fvwm crashes today with one program and could get it down
to a FVWM issue:
[snip]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7ba58c0 (LWP 20284)]
0x080aadcf in ewmh_MoveResizeWindow (fw=0x0, ev=0x80fb180, style=0x0, any=0)
at ewmh_events.c:194
194 if (
(gdb) bt
#0 0x080aadcf in ewmh_MoveResizeWindow (fw=0x0, ev=0x80fb180, style=0x0,
any=0) at ewmh_events.c:194
#1 0x080a9aaa in EWMH_ProcessClientMessage (exc=0x8119670)
at ewmh_events.c:1485
#2 0x0806f380 in HandleClientMessage (ea=0xbfd84a14) at events.c:1805
#3 0x0806c031 in dispatch_event (e=0xbfd84a44) at events.c:3969
#4 0x0806c73f in HandleEvents () at events.c:4010
#5 0x0808cba5 in main (argc=1, argv=0xbfd854c4) at fvwm.c:2597
(gdb) quit
I have compiled a fresh FVWM CVS checkout from 2 hours ago.
If I can be of any help diagnosing the problem, please tell me how I can help.
I have just committed a fix for that crash. Can you try the most
recent CVS code?
ok. That seems to fix this issue.
Only little glitch was in your patch:
[EMAIL PROTECTED]:~/fvwm/src/fvwm$ cvs diff
Index: fvwm/ewmh_events.c
===================================================================
RCS file: /home/cvs/fvwm/fvwm/fvwm/ewmh_events.c,v
retrieving revision 1.58
diff -u -1 -b -p -r1.58 ewmh_events.c
--- fvwm/ewmh_events.c 30 Jan 2008 21:18:35 -0000 1.58
+++ fvwm/ewmh_events.c 31 Jan 2008 09:01:30 -0000
@@ -213,3 +213,3 @@ int ewmh_MoveResizeWindow(EWMH_CMD_ARGS)
do_reconfigure = !!is_function_allowed(
- func, NULL, fw, RQORIG_PROGRAM, False))
+ func, NULL, fw, RQORIG_PROGRAM, False);
}
Thanks
Philipp
