Re: What does this mean?

Sascha Schumann <sascha@schumann.cx> writes: > That's why I like dmalloc. I suggested this once to Zeev, but > it has not been implemented yet. Ok, apparently it's only called once and this is the result: (gdb) p sapi_header $3 = (sapi_header_struct *) 0x86383b8 *(gdb) p *sapi_header $4 = {header = 0x8638310 'Z' <repeats 28 times>, "ðÜ>\b\204Ì\217*Q", header_len = 27} Weird header if you ask me. :-) Hmm. Ahh, I see what the problem is. I had a efree(sapi_header->header) in php_roxen_sapi_header_handler (originally from aolserver.c). When deleting the line the error message went away. When replacing it with sapi_free_header(sapi_header) (which is what aolserver.c has now), the error came back. So I gather that I really shouldn't free anything there? Or does the return code have any significance? I return 1 there for some reason, while aolserver.c returns 0. *test* Yeps, seems like when I return 0 from that function, the header isn't freed twice. IT was the X-Powered-By header btw. -- [ Below is a random fortune, which is unrelated to the above message. ] I THINK THEY SHOULD CONTINUE the policy of not giving a Nobel Prize for paneling. -- Jack Handley, The New Mexican, 1988.