[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-debug-dev] Debugging outside CDT project
|
One of the things that have improved tremendously lately is debugging
code outside a CDT project(both with and without source code).
To have first class support for debugging code outside CDT projects is a
crucial part of supporting embedded debugging.
When suspending a target with a hardware debugger(e.g. JTAG debugger),
the CPU is suspended on the very next instruction, which could be
anywhere, and oftentimes is inside an interrupt, exception handler etc.
At this point disassembly/single-stepping is crucial.
E.g. to establish where the interrupt came from, it is often necessary
to single step a bit further to get enough context information. If there
is any source code for the interrupt handler, it may very well be
outside the CDT project.
Obviously the application stack frame concept breaks down when stepping
into and out of interrupts/exceptions/thread switches, etc., so it is
important that CDT deals gracefully with weird stack frame replies from
GDB.
--
Øyvind Harboe
http://www.zylin.com
