Patch to propagate GDB's knowledge of the executing state to frontend
ali_anwar
ali_anwar@codesourcery.com
Thu Oct 25 11:10:00 GMT 2012
Hi,
Attached patch is to let GDB propagate the target state under following
two scenarios:
1. Attached patch will enable GDB to inform about the state of the
target when it was not able to fetch the non-general registers, when
target is already stopped.
The reason behind this behavior was an error message which was caused
when the GDB was not able to fetch the value of a certain register. The
GDB should have told the front end about the current state of the
target. The attached patch makes sure that it happens. This patch should
be a safety measure in case some debugging stub behaves badly.
2. Attached patch will enable GDB to inform about the state of the
target when it was not able to fetch the backtrace once the step has
already occurred and target is in stopped state.
I have tested the patch for powerpc-eabi as well as i686-pc-linux. No
regression was introduced by the patch and results were identical with
and without the patch.
The patch has also been tested with both sync and async mode, no regression.
OK?
Thanks,
-Ali
-------------- next part --------------
A non-text attachment was scrubbed...
Name: target_state.patch
Type: text/x-patch
Size: 2474 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20121025/ed1783f3/attachment.bin>
More information about the Gdb-patches
mailing list