In Debug mode, MSVC wraps each alloc with guard space before and after,
to enable checks for illegal overruns or underruns to be made. This does
not happen in Release mode. These error messages general mean that array
boundaries are being exceeded, but can also be generated if ther is an
attempt to free memory twice. The clue to this is the special value
expected, eg 0xFD. As I am writing this from memory, I can't remember
offhand which value means which. But that is what these messages mean.

Richard Dobson



Gabriel Maldonado wrote:
> 
> Dear Jpff,
> two questions about new score opcodes:
> 
> 1) Another nice thing to do is to implement nested repeats.
> I will be very happy if you will implement such feature.
> 
> 2) When I use the debug mode with MSVC, the compiler displays a lot of error messages when
> using macros:
> 
> memory check error at 0x00851C88 = 0x30, should be 0xFD
> 
> I noticed that these messages are generated by a free() call, in particular by:
> 
> mfree(str->body);
> 
> in file SREAD.C
> 
> These errors doesnt appear in release compilation. Have you any idea?
> 
> Gab

-- 
Test your DAW with my Soundcard Attrition Page!
http://wkweb5.cableinet.co.uk/rwd