diff options
| author |   Ajit Kumar Agarwal <ajitkum@xilinx.com> | 2014-10-10 18:07:06 +0100 |
|---|---|---|
| committer |   Pedro Alves <palves@redhat.com> | 2014-10-10 18:07:06 +0100 |
| commit | cc3afae25a4e37ed7a864a8f4eea1dc11b20d5fb (patch) | |
| tree | 0a3a2fe7074877b0a957b587ad973e926adfe653 /gdb/configure | |
| parent | Cache the vsyscall/vDSO range per-inferior (diff) | |
| download | binutils-gdb-cc3afae25a4e37ed7a864a8f4eea1dc11b20d5fb.tar.gz binutils-gdb-cc3afae25a4e37ed7a864a8f4eea1dc11b20d5fb.tar.bz2 binutils-gdb-cc3afae25a4e37ed7a864a8f4eea1dc11b20d5fb.zip | |
Microblaze: Reject invalid target descriptions
We currently validate the target description, but then forget to
reject it if found invalid.
Tested that incorrect descriptions are rejected and GDB warns about
them.
Tested the Microblaze Design with and without stack-protect registers.
The gdb command "info registers" displayed the register correctly. If
a stack protect design is not selected, only core registers are
displayed. When the stack-protect registers are selected in the
design, the core registers along with stack-protect registers are
displayed.
gdb/
2014-10-10 Ajit Agarwal <ajitkum@xilinx.com>
* microblaze-tdep.c (microblaze_gdbarch_init): If the description
isn't valid, release the tdesc arch data and return NULL.
Diffstat (limited to 'gdb/configure')
0 files changed, 0 insertions, 0 deletions