After hunting through bunches of .h files (debugging with all
those macros is a real pain), I finally figured out, that
calling perl_alloc with EMBED+DEBUG+MULTIPLICITY is not a
good idea:
perl_alloc uses safemalloc, and safemalloc (with the above
mentioned combination of flags) uses DEBUG_m, which then
turns out to do something like (debug & 128), where debug
is in fact (curinterp->Idebug). curinterp however does not
exist yet, since perl_alloc is just in the process of
allocating it...
How in h... do you guys stand debugging perl C code? Are
there debuggers that actually read all those macros? Or
do you just know the important ones after a while?
Oh well, I feel better now.
gerti
those macros is a real pain), I finally figured out, that
calling perl_alloc with EMBED+DEBUG+MULTIPLICITY is not a
good idea:
perl_alloc uses safemalloc, and safemalloc (with the above
mentioned combination of flags) uses DEBUG_m, which then
turns out to do something like (debug & 128), where debug
is in fact (curinterp->Idebug). curinterp however does not
exist yet, since perl_alloc is just in the process of
allocating it...
How in h... do you guys stand debugging perl C code? Are
there debuggers that actually read all those macros? Or
do you just know the important ones after a while?
Oh well, I feel better now.
gerti