Front page | perl.perl5.porters |
Postings from November 1999
Hi! > > But the free() is called with the pointer to a memory block which has > > never been malloc()'ed by perl. > > You look utterly confused. First you claim that this is not a problem > with several mismatched malloc()s, now you say that it is. Nope. All I say is that you MUST NOT free() memory which hasn't been malloc()ed before. The memory block which perl tries to free() in Safefree() is the original block passed via exec(2). This block hasn't been malloc()ed and therefore perl must not free() it. > Please decide which way you want to argue first. All you write > confirms what we were explaining you several times: your Perl is using > Perl's malloc(), and your patch has no relationship to how things happen. Diddn't you get the output of my "perl -V"? It clearly states "usemymalloc=n". Regards, Joerg -- Gaertner Datensysteme 38114 Braunschweig Joerg Schumacher Hamburger Str. 273a Tel: 0531-2335555 Fax: 0531-2335556