diff options
| author | Tiezhu Yang <yangtiezhu@loongson.cn> | 2022-05-09 16:26:47 +0800 |
|---|---|---|
| committer | Tiezhu Yang <yangtiezhu@loongson.cn> | 2022-05-09 22:33:44 +0800 |
| commit | 0b8c95579f78b352cd48cc14e48ea842c64a7a5a (patch) | |
| tree | e0825b28a90d0ea6d5db0d732c794ac93b1d5cc4 /symlink-tree | |
| parent | 205d0542821c91e04e0ed174d8862f486a076950 (diff) | |
| download | gdb-0b8c95579f78b352cd48cc14e48ea842c64a7a5a.zip gdb-0b8c95579f78b352cd48cc14e48ea842c64a7a5a.tar.gz gdb-0b8c95579f78b352cd48cc14e48ea842c64a7a5a.tar.bz2 | |
gdb: LoongArch: Implement the return_value gdbarch method
When execute the following command on LoongArch:
make check-gdb TESTS="gdb.base/async.exp"
there exist the following failed testcases:
FAIL: gdb.base/async.exp: finish& (timeout)
FAIL: gdb.base/async.exp: jump& (timeout)
FAIL: gdb.base/async.exp: until& (timeout)
FAIL: gdb.base/async.exp: set exec-done-display off (GDB internal error)
we can see the following messages in gdb/testsuite/gdb.log:
finish&
Run till exit from #0 foo () at /home/loongson/gdb.git/gdb/testsuite/gdb.base/async.c:9
(gdb) /home/loongson/gdb.git/gdb/gdbarch.c:2646: internal-error: gdbarch_return_value: Assertion `gdbarch->return_value != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
In order to fix the above failed testcases, implement the return_value
gdbarch method on LoongArch.
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Diffstat (limited to 'symlink-tree')
0 files changed, 0 insertions, 0 deletions