stack trace?

[Guest slowphones]

Does anyone know the memory address of the stack or a way of logging it? The "call stack" is ok for functions you are calling but doesn't show me what i need to know about them returning and where its going wrong :?

Thanks

[Guest spacemonkey]

Can't help your specific problem.

But, I found the debugger in general approach was a bit of a pain as it seems to get very unstable. A good old fashioned approach is to just log stuff to a text file and here's an easy way to do it:

http://www.smartphonedn.com/articles/stlog.html

Add in the header and then it's just a call anywhere you want a log entry with printf formating so you can dump variables and stuff.