| Useful call
stacks from Hardware |
|
|
|
|
|
|
|
|
|
|
|
|
|
| • | To get a useful
call stack two things are |
|||||||||||
| always
needed. |
||||||||||||
| … | A hex dump of the
memory used by the stack of |
|||||||||||
| the thread which
paniced |
||||||||||||
| … | A ROM symbol file
for the software flashed onto |
|||||||||||
| the device. |
||||||||||||
| • | With this
information a Symbian perl script |
|||||||||||
| can decode a
human readable call stack ( |
||||||||||||
| similar to the
call stack seen in the emulator). |
||||||||||||
|
|
|
|
| Note:
The symbol file must match the software in the |
|||
| ROM,
if you built the ROM yourself, you already have |
|||
| the
symbol file. If it is a release ROM or another |
|||
| developer - you
must ask for the symbol file. |
|||
