Atom/Third tools

[Ian Kirkham]

I have a need to debug some memory corruption bugs in an application that uses its own memory manager. Third would do what I want apart from the fact that my application is not using malloc/free. To this end I have written analysis code to help but have had hit the problem of needing to know the call stack. This has proven really awkward as routines such as exc_virtual_unwind seem unhappy and I note that even ladebug has problems examining the stack from within an analysis routine.
Any help or hints would be appreciated.

I wonder if there any plans to release third as an example application?

Regards,
Ian

[Ian Kirkham]

Is there not anyone else who uses atom?