On Wed, Dec 11, 2002 at 02:40:02PM -0500, Dan Espen wrote: > > I've been working with Tomi on the premature close of OpenInterface > GUI problem without much success. I've been able to recreate the > problem once or twice but not very consistently. > > I've never created the problem with gdb attached or with debug > information printing. Even without gdb or debug, its not consistent. > > Anyway, I'll keep at it. > > Since I saw inconsistent behavior I thought it might help to do some > Fvwm runs with Purify. I don't think I'm going to be able to use > Purify with the GUI in question due to some firewall issues, but I did > run a few GUIs with child windows, resize windows, iconify windows > switch pages, and pop up menus. > > 2.5.6 looked pretty good. All I see are a few UMRs. (Uninitialized > Memory Reads.) Often UMRs aren't a problem. Its fine to copy > uninitialized memory. As long as you aren't doing tests against that > memory there is no problem.
While you're at it, please try out the new window shade features. > Here are the UMRs: > > UMR: Uninitialized memory read: > * This is occurring while in: > __execute_function [functions.c:545] > execute_function [functions.c:1176] > StartupStuff [fvwm.c:1498] > My_XNextEvent [events.c:3320] > HandleEvents [events.c:3240] > main [fvwm.c:2412] > _start [crt1.o] > * Reading 4 bytes from 0x2c7480 in the heap. > * Address 0x2c7480 is 16 bytes into a malloc'd block at 0x2c7470 of 124 > bytes. > * This block was allocated from: > malloc [rtlib.o] > calloc [rtlib.o] > safecalloc [safemalloc.c:64] > exc_create_null_context [execcontext.c:96] > exc_create_context [execcontext.c:117] > StartupStuff [fvwm.c:1465] > My_XNextEvent [events.c:3320] > HandleEvents [events.c:3240] > main [fvwm.c:2412] > _start [crt1.o] I don't understand this one. What code do you have in functions.c, line 545? > UMR: Uninitialized memory read: > * This is occurring while in: > _SetFocusWindow [focus.c:922] > > UMR: Uninitialized memory read: > * This is occurring while in: > DrawIconPixmapWindow [icons.c:1012] Should both the "fixed". They are not really UMRs. Purify seems to be unable to handle btructs with bit fields properly. Bye Dominik ^_^ ^_^ -- 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]
