aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdb_expat.h
diff options
context:
space:
mode:
authorGustavo Romero <gustavo.romero@linaro.org>2024-04-18 20:10:37 +0000
committerLuis Machado <luis.machado@arm.com>2024-04-19 15:29:40 +0100
commitc040e0b107ca023b434746719d83bc9a3ad94276 (patch)
tree5623086d933a1de7c3932a282ba12b41270676e8 /gdb/gdb_expat.h
parent7202f41f5f4393eec37747cc2c46673cfaa74d72 (diff)
downloadgdb-c040e0b107ca023b434746719d83bc9a3ad94276.zip
gdb-c040e0b107ca023b434746719d83bc9a3ad94276.tar.gz
gdb-c040e0b107ca023b434746719d83bc9a3ad94276.tar.bz2
gdb: Add qIsAddressTagged packet
This commit adds a new packet, qIsAddressTagged, allowing GDB remote targets to use it to query the stub if a given address is tagged. Currently, the memory tagging address check is done via a read query, where the contents of /proc/<PID>/smaps is read and the flags are inspected for memory tagging-related flags that indicate the address is in a memory tagged region. This is not ideal, for example, for QEMU stub and other cases, such as on bare-metal, where there is no notion of an OS file like 'smaps.' Hence, the introduction of qIsAddressTagged packet allows checking if an address is tagged in an agnostic way. The is_address_tagged target hook in remote.c attempts to use the qIsAddressTagged packet first for checking if an address is tagged and if the stub does not support such a packet (reply is empty) it falls back to using the current mechanism that reads the contents of /proc/<PID>/smaps via vFile requests. Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org> Approved-By: Luis Machado <luis.machado@arm.com> Tested-By: Luis Machado <luis.machado@arm.com>
Diffstat (limited to 'gdb/gdb_expat.h')
0 files changed, 0 insertions, 0 deletions