|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (2) » Build tools (1) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (1) » Carbide Plug-Ins (2) » CodeWarrior (2) » FAQ (5) » Future directions (19) » General (44) » Off-topic (4) » On-device debugging (10) » Performance Investigator (2) » Product features (15) » Product releases (16) » Screencast (8) » Support (23) » Tool setup (5) » UI Designer (8) » Usability (11) » Work in Progress (11) » Write-build-debug (4) |
|
» Online Carbide documentation push » Panic Debugging » Screencast: Carbide Perspectives » Event secrets in PI » Performance |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Screencast: Carbide Perspectives | Main | Online Carbide documentation push »
In Carbide 1.3 we now display information when a panic has occurred when doing on-device debugging.
The user will now see the stack crawl display that a panic has occurred. The panic number is shown in the StackCrawl-Thread information at the top. The top frame will be the User::Panic() code. It will have source if Euser has symbolics and disassembly otherwise. The next frame will be the caller of User::Panic() only if symbolics exist for that location. Otherwise it will be in disassembly. The application will exit and the debug session will terminate when the user resumes.
You will need version 2.8.7 of TRK if debugging with Series 60 phones, which is the version of Application TRK that we shipped with the tools. The current 2.8 version of UIQ 3.0 Application TRK does not have this feature but it will be incorporated into the next release of the TRK.
Note that the stack crawl reconstruction depends on having symbolics for the caller of User::Panic(). If there is no symbolics (the library does not have a .sym file), then the stack crawl cannot be reconstructed properly.
