On 19 Apr 2002 16:23:59 +0100, Tim Phipps wrote: > > This probably won't fix your problems, if it doesn't you should be able > to get a core dump by starting fvwm with the -debug flag to get > synchronous behaviour and then putting "abort();" in the error handler > routine (fvwm.c line 1762).
I upgraded my gcc and gdb and now I get non-empty stack traces. So I may send any stack trace. But I think you may reproduce this error [FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error *** [FVWM][FvwmErrorHandler]: <<ERROR>> Request 56, Error 13, EventType: 0 using this minimal config (fvwm -f colorset-bug): ModuleSynchronous FvwmTheme *FvwmTheme: Colorset 1 fg black, bg gray50, VGradient 30 gray40 gray60 You may switch these lines - the same result. Now, if you remove a comma after "black" or remove fg and bg parts altogether you get core dump. I think this is because image is NULL in line 586 of colorset.c. Regards, Mikhael. -- 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]
