Carbide + S60 SDK: How to see the call stack

Login to reply to this topic.
Wed, 2006-10-18 07:21
mteppo
Joined: 2006-10-18
 Forum posts: 2
Hi,

I'm new to carbide enviromnent, and I would like to know if anyone came across a faq or other topic that explains how to get the unhandled exceptions into the debugger so that the code would not just exit. (Just in Time-debugging)
This used to happen automatically with VC++ and pre S60 SDK's. Now I'm not sure if it happened with CodeWarrior. Or is it so that my memories are golden   Undecided

What I have now is \Symbian\9.2\S60_3rd_FP1 - SDK and Carbide.c++ v1.1

I have been using the Birthday example as the source for this experiment - it comes with the carbide.
The way to reproduce this problem is to delete all entries from the list view and then select "Edit" from the menu.
I know the problem on the example comes from buggy code not expecting -1 being an index value - this is trivial.

What I'm asking is if there is any way that the code would not stop the execution because of this problem but just "halt" and I could see the call stack which is very much about to launch the exception.

Or was this a dream and now I'm awake?

Wed, 2006-10-18 12:21
mteppo
Joined: 2006-10-18
 Forum posts: 2
Re: Carbide + S60 SDK: How to catch unhandled exceptions?
OK - now I got to the point of actually getting the tread-in-question to halt.

How do I get the call-stack readable. Or at least get more info on the stack frame so I can see some pointers etc that must be present in a debug build I am using.
Friend of mine I discussed this with said that the problem could be resolved by using CodeWarrior as well.

 
  • Login to reply to this topic.