Interpreter or Win32Lib bug?
- Posted by Brian Broker <bkb at cnw.com> Mar 11, 2003
- 513 views
I did notice the following while playing with Win32Lib version 0.58.02. Programs that have a "with trace" statement in them will crash with an error similar to the partial ex.err below. If the "with trace" statement is commented, the program runs fine. Does this have anything to do with Win32Lib's memory handling? This was produced from ex10.exw: e:\euphoria\include\win32lib\include\tk_mem.e:601 in procedure manage_mem() A machine-level exception occurred during execution of this statement pOwner = 0 pAddr = 3612308 lOwnerSub = 1 lAddrSub = 0 i = 1 ... called from e:\euphoria\include\win32lib\include\tk_mem.e:675 in function acquire_mem() pOwner = 0 pData = {99'c',111'o',109'm',109'm',100'd',108'l',103'g',95'_',70'F', 105'i',110'n',100'd',82'R',101'e',112'p',108'l',97'a',99'c',101'e'} at = 3612308 ... called from e:\euphoria\include\win32lib\include\w32comdlg.ew:19