BUG? PyMem_Free vs strdup

[Michael Hudson]

Robin Becker <robin at jessikat.fsnet.co.uk> writes:

> I am trying a debugging version of Python 2.3 under win32. In my
> extension I am getting a memory checking debug interrupt when attempting
> to free a string that was allocated using strdup.

In a debug build *all* allocations that Python does go via pymalloc.

> I don't think I've done something to change the bytes, but can I mix
> strdup allocated memory with the "Python heap" which is what the manual
> talks about or is this a bug? 

Doesn't look like it!

Cheers,
mwh

-- 
  For their next act, they'll no doubt be buying a firewall 
  running under NT, which makes about as much sense as 
  building a prison out of meringue.                     -- -:Tanuki:-
               -- http://home.xnet.com/~raven/Sysadmin/ASR.Quotes.html