1/1
debug unit should indicate which checkpoint caused the trap
by Unknown on Feb 4, 2004 |
Not available! | ||
I've got most of gdb stub implemented to use hard break- and
watchpoints. There is one place where gdb wants to know whether a breakpoint, access watch or read watch was hit, and also the data address in case of a watchpoint. I can't really figure that out with the registers of the current debug unit. I would need a set of bits that indicate which checkpoint matched the processor state when the trap was generated. Is that possible, Damjan? Heiko |
1/1