On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote:
>"Boris Popov" <[EMAIL PROTECTED]> wrote:
>>
>> Does this help at all?
>>
>
>No. A stack trace, especially one without line number
>information, is of no help whatsoever.
I beg to differ. Any stack trace that includes malloc or free is almost
certainly heap corruption. What the OP should do is:
- Check for buffer overflows.
- Check for multiple free()s of the same memory block.
- Run the software under some memory checker. Not sure what to recommend
on Windows.
The problem is almost certainly in the OP's code.
>D. Richard Hipp <[EMAIL PROTECTED]>
Christian
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
