RetroSearch Browse

Thu Sep 8 20:35:35 EDT 2005 · http://mail.python.org/pipermail/python-list/2005-September/306203.html

"Fredrik Lundh" <fredrik at pythonware.com> writes:

> Lil wrote:'
>
>>I already double checked my C code. It runs perfectly fine in C without
>> any errors. So in my python program, I added a pdb.set_trace()
>> and step through the program and it did not dump. But when i took out
>> the tracing, the core dump came back. "sigh"
>
> so triple-check it.
>
> if your code overwrites the malloc buffer, it's perfectly possible
> that it appears to run fine when you run it standalone or under the
> debugger, but that doesn't mean that your code is fine.

The appropriate aphorism is: "Testing can never reveal the absence of
bugs."

        <mike
-- 
Mike Meyer <mwm at mired.org>			http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-list/2005-September/306203.html below:

Help! Python either hangs or core dumps when calling C malloc