diff options
| author | Pedro Alves <palves@redhat.com> | 2016-03-08 01:45:09 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2016-03-09 03:14:07 +0000 |
| commit | 114d7832b0e07452277d748c81d8bc0c5675a1bc (patch) | |
| tree | 63d2ce66e42ce324d7c4508d972e1bdbfd236645 /cpu/fr30.opc | |
| parent | d7a87b5e4343467db23b70e73b156c9cc79c50ea (diff) | |
| download | gdb-114d7832b0e07452277d748c81d8bc0c5675a1bc.zip gdb-114d7832b0e07452277d748c81d8bc0c5675a1bc.tar.gz gdb-114d7832b0e07452277d748c81d8bc0c5675a1bc.tar.bz2 | |
[CRIS] Don't internal error if forced big endian
This fixes:
$ ./gdb -q -ex "set endian big" -ex "set architecture cris"
The target is assumed to be big endian
.../src/gdb/cris-tdep.c:4051: internal-error: cris_gdbarch_init: big endian byte order in info
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
The "set cris-version" command can likewise cause internal errors.
The gdbarch init routine should be returning 0 to reject the
architecture instead of internal erroring on user input.
gdb/ChangeLog:
2016-03-09 Pedro Alves <palves@redhat.com>
* cris-tdep.c (cris_gdbarch_init): Return 0 if the info's byte
order is BFD_ENDIAN_BIG or if the cris version is unsupported.
Diffstat (limited to 'cpu/fr30.opc')
0 files changed, 0 insertions, 0 deletions