[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Coroutines and C stack traces.
- From: Antero Vipunen <antero@...>
- Date: Fri, 12 Aug 2005 14:17:13 +0700
Try using some sort of memorydebugger like valgrind (yes i know that you
are using windows not linux, but there must be some replacements).
There is no way for us to find bug in _your_ code. Only complete source
code contains sufficient information to do that. We are not telepaths,
not Gods either.
David Morris-Oliveros wrote:
i'm getting very reproducible memory corruption
_somewhere_. This is visible in a totally corrupt stack trace
during reproducible crashes.