Thank you very much, Romiras.
I am able to reproduce the problem and will have a look into it.
Thanks again,
Marc
________________________________
From: BlackBox [mailto:BLACKBOX{([at]})nowhere.xy
Sent: Montag, 3. September 2012 01:06
To: BLACKBOX{([at]})nowhere.xy
Subject: Re: [BLACKBOX] FW: [BLACKBOX] Windows 7
I still can reproduce a memory allocation bug with following code:
MODULE TestNewArr;
PROCEDURE Do*;
VAR ptr : POINTER TO ARRAY OF REAL;
BEGIN
NEW(ptr, 07FFCH);
END Do;
BEGIN
Do
END TestNewArr.
I have compiled a new Kernel and then builded test console application by command
DevLinker.Link dos testalloc.exe := Kernel$+ TestNewArr~
It failes in CheckCandidates. But if I use an original (CP) version of procedure Next, I get error from it: "illegal memory read [ad = 00000000]". Tested on Windows XP SP3 in both physical machine with 2GB and virtual machine with 384MB RAM. Same bug when running testalloc under Wine in Linux.
2012/8/29 Marc Frei <frei{([at]})nowhere.xy
For folks willing to help testing the corrections mentioned in my last mail, I herewith forward the patch we previously sent out to Robert.
Thank you very much in advance,
Marc
-----Original Message-----
From: Blackbox Support Oberon microsystems AG
Sent: Mittwoch, 22. August 2012 12:01
To: robert.d.campbell{([at]})nowhere.xy
Subject: RE: [BLACKBOX] Windows 7
Dear Robert,
finally, we have a patch ready that should fix critical errors in several cases of memory allocations that led to integer overflows in the kernel and compiler. We still cannot entirely explain the differences between 32-bit Windows XP and 64-bit Windows 7 you have been observing but it would be very valuable if you could try this patch with your software on your system:
- Please download and install a fresh copy of BlackBox 1.6-rc6 from
http://www.oberon.ch/zip/SetupBlackBox16-rc6.exe
- Apply the StdCoder encoded text in the attachment.
- Link a new version of BlackBox with the following command
DevLinker.Link BlackBox2.exe := Kernel$+ Files HostFiles StdLoader
1 Applogo.ico 2 Doclogo.ico 3 SFLogo.ico 4 CFLogo.ico 5 DtyLogo.ico 6 folderimg.ico 7 openimg.ico 8 leafimg.ico 1 Move.cur 2 Copy.cur 3 Link.cur 4 Pick.cur 5 Stop.cur 6 Hand.cur 7 Table.cur
- Quit BlackBox, delete the old BlackBox.exe and rename BlackBox2.exe to BlackBox.exe.
- Start the new BlackBox.exe and recompile all your modules. It is possible that you will encounter new compiler errors in cases of memory allocations with statically detectable integer overflows.
- Test your recompiled modules. It is possible that you will encounter memory allocations that return NIL pointers in cases where there is not enough memory available but there should be no low-level traps in the module Kernel anymore. You should handle the out of memory situations indicated by NIL pointers returned from NEW in your application code. (BlackBox cannot allocate more than a total of approximately 1.5GB of heap memory.)
Thank you very much for your help and kind regards,
Marc
----
To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
Received on Mon Sep 03 2012 - 09:22:48 UTC