Re: Coroutines and C stack traces.

[David Morris-Oliveros <david@...>]

I just wanted to know if i was doing something ridiculously wrong in the 
way i was creating threads.

Sorry to cause the trouble.

Antero Vipunen wrote:

> 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.
>
> AMDG,
>  Antero Vipunen.
>
> David Morris-Oliveros wrote:
>
> > i'm getting very reproducible memory corruption
> > _somewhere_. This is visible in a totally corrupt stack trace
> > during reproducible crashes.

--
// David Morris-Oliveros
// Camera & Lua Coder
// Team Bondi


------------------------------------------------------------------------
Contact:
Team Bondi Pty Ltd
Level 2, 608 Harris Street
Ultimo, NSW 2007
Australia
Tel: +61 (0)2 8218 1500
Fax: +61 (0)2 8218 1507
Web: http://www.teambondi.com
------------------------------------------------------------------------
This email may contain confidential information.  If you are not
the intended recipient, you may not copy or deliver this message to
anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Opinions, conclusions and other
information in this message that do not relate to the official business
of our firm shall be understood as neither given nor endorsed by it.
------------------------------------------------------------------------