diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-07-27 13:06:38 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-08-01 13:00:57 -0600 |
| commit | 2128d888b888b04edb4553a5359e6e259c792606 (patch) | |
| tree | 306541d476c371991ce6a21b309e3c8a290060d9 /binutils/dwarf.c | |
| parent | af93035b2755fef31c67016f68ab9fcdc2074c42 (diff) | |
| download | gdb-2128d888b888b04edb4553a5359e6e259c792606.zip gdb-2128d888b888b04edb4553a5359e6e259c792606.tar.gz gdb-2128d888b888b04edb4553a5359e6e259c792606.tar.bz2 | |
Respect supportsMemoryReferences in DAP
I noticed that the support for memoryReference in the "variables"
output is gated on the client "supportsMemoryReferences" capability.
This patch implements this and makes some other changes to the DAP
memory reference code:
* Remove the memoryReference special case from _SetResult.
Upstream DAP fixed this oversight in response to
https://github.com/microsoft/debug-adapter-protocol/issues/414
* Don't use the address of a variable as its memoryReference -- only
emit this for pointer types. There's no spec support for the
previous approach.
* Use strip_typedefs to handle typedefs of pointers.
Diffstat (limited to 'binutils/dwarf.c')
0 files changed, 0 insertions, 0 deletions