This is annoyingly verbose in when connected to
a target that is failing poll... otherwise it's ok.
This is really a message that should be displayed in GDB only,
but there is no mechanism today to check if there is a gdb session
associated... Perhaps adding a "reason" to the event reporting
mecha
Print reason why GDB halts.
1. srst detected:
(gdb) c
Continuing.
Waking up GDB, srst asserted detected.
[Thread ] #1 stopped.
0xda42bf3c in ?? ()
2. failed to poll:
(gdb) c
Continuing.
Failed to poll target, halting GDB.
[Thread ] #1 stopped.
0x0004 in ?? ()
--
Øyvind Harboe
US toll
