diff options
| author | Andrew Burgess <andrew.burgess@embecosm.com> | 2020-09-16 10:12:39 +0100 |
|---|---|---|
| committer | Lifang Xia <xlf194833_xia@alibaba-inc.com> | 2020-09-17 14:52:05 +0800 |
| commit | c568ac5ff708eebf6ef424e5863d3dbd874a3f62 (patch) | |
| tree | 160bb166250bfb409f8a9481e5d55cedbd92490f /gdb/main.c | |
| parent | c2f876e11e5c9cc818a852bd79452ffdc80bc161 (diff) | |
| download | gdb-c568ac5ff708eebf6ef424e5863d3dbd874a3f62.zip gdb-c568ac5ff708eebf6ef424e5863d3dbd874a3f62.tar.gz gdb-c568ac5ff708eebf6ef424e5863d3dbd874a3f62.tar.bz2 | |
opcodes/csky: return the default disassembler when there is no bfd
The disassembler function should return a valid disassembler function
even when there is no BFD present. This is implied (I believe) by the
comment in dis-asm.h which says the BFD may be NULL. Further, it
makes sense when considering that the disassembler is used in GDB, and
GDB may connect to a target and perform debugging even without a BFD
being supplied.
This commit makes the csky_get_disassembler function return the
default disassembler configuration when no bfd is supplied, this is
the same default configuration as is used when a BFD is supplied, but
the BFD has no attributes section.
Before the change configuring GDB with --enable-targets=all and
running the tests gdb.base/all-architectures-2.exp results in many
errors, but after this change there are no failures.
opcodes/ChangeLog:
* csky-dis.c (csky_get_disassembler): Don't return NULL when there
is no BFD.
Diffstat (limited to 'gdb/main.c')
0 files changed, 0 insertions, 0 deletions