aboutsummaryrefslogtreecommitdiff
path: root/opcodes/mt-opc.h
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2018-03-02 15:48:23 +0000
committerAndrew Burgess <andrew.burgess@embecosm.com>2018-03-06 09:59:08 +0000
commit5dc4391345f6e86906a57af1434025cfb47b4100 (patch)
treea9080df418b124274748016acf17f7895970c236 /opcodes/mt-opc.h
parent52bc7e85d938e7a6582d31eca071e43429d6fb00 (diff)
downloadgdb-5dc4391345f6e86906a57af1434025cfb47b4100.zip
gdb-5dc4391345f6e86906a57af1434025cfb47b4100.tar.gz
gdb-5dc4391345f6e86906a57af1434025cfb47b4100.tar.bz2
gdb/amd64: Ignore zero sized fields when calling functions
In some cases passing an argument to a function on amd64, or attempting to fetch the return value, can trigger an assertion failure within GDB. An example of a type that would trigger such an error is: struct foo_t { long double a; struct { struct { /* Empty. */ } es1; } s1; }; GCC does permit empty structures, so we should probably support this. The test that exposes this bug is in the next commit along with the RiscV support. gdb/ChangeLog: * amd64-tdep.c (amd64_classify_aggregate): Ignore zero sized fields within aggregates.
Diffstat (limited to 'opcodes/mt-opc.h')
0 files changed, 0 insertions, 0 deletions