On Thu, 13 Nov 2014 10:08:47 +0000
Chris via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote:

> Interesting though that it never crashes on Linux, only on 
> Windows did this cause problems.
seems that libc allocator is not marking free pages as "unreadable",
and windows libc allocator does something like this. i got alot of such
"use after free" things in my C code, but valgrind is brilliant to
track that down. i miss valgrind on windows. ;-)

now i prefer to write code in GNU/Linux if possible and use valgrind to
track down memory issues, and only after it works on linux and valgrind
is happy, i'm starting to port it to windows. this, of course, hard to
do with winapi-tied code, but wine/winelib can help there too (to some
extent).

Attachment: signature.asc
Description: PGP signature

Reply via email to