NewLC - Tracking down hardware exceptions on hardware - Comments

Re: Tracking down hardware exceptions on hardware

Mark139 — Thu, 06 Dec 2007 09:49:00 +0100

There is a class of debugging technique missing. The Solaris (and now MacOS X) DTrace. In summary this allows a developer to insert tracing into any code (including system code) at run time without much penalty in performance. There is a simple macro language available for programming the traces. It's a simple and elegant solution to an age old problem
Hopefully, one day Symbian will give us a similar tool.

Re: Tracking down hardware exceptions on hardware

alh — Wed, 05 Dec 2007 10:28:05 +0100

Nice summary!
I realize this is meant to be a pretty general description to aid understanding of what can happen and what options are available.
But could be helpful though if it was a bit more clear what things is possible to do as a 3rd party, and what needs partner privileges, etc to get access to the tools needed.

Tracking down hardware exceptions on hardware

raghav_an — Mon, 03 Dec 2007 23:29:26 +0100

Hardware exceptions are abnormal events triggered by the ARM instruction being executed. The sources of this can be accessing non-existing memory, accessing mis-aligned memory, writing to a read-only area of memory, jumping to invalid memory address, local stack overflow and so forth.
Tracking down hardware exceptions is a developer’s nightmare.