mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-27 04:52:05 +08:00
68cffbbd44
Teach GDB how to dump memory tags for AArch64 when using the gcore command and how to read memory tag data back from a core file generated by GDB (via gcore) or by the Linux kernel. The format is documented in the Linux Kernel documentation [1]. Each tagged memory range (listed in /proc/<pid>/smaps) gets dumped to its own PT_AARCH64_MEMTAG_MTE segment. A section named ".memtag" is created for each of those segments when reading the core file back. To save a little bit of space, given MTE tags only take 4 bits, the memory tags are stored packed as 2 tags per byte. When reading the data back, the tags are unpacked. I've added a new testcase to exercise the feature. Build-tested with --enable-targets=all and regression tested on aarch64-linux Ubuntu 20.04. [1] Documentation/arm64/memory-tagging-extension.rst (Core Dump Support) |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| a4rc.sed | ||
| agentexpr.texi | ||
| all-cfg.texi | ||
| annotate.texinfo | ||
| ChangeLog-1991-2021 | ||
| doxy-index.in | ||
| Doxyfile-base.in | ||
| Doxyfile-gdb-api.in | ||
| Doxyfile-gdb-xref.in | ||
| Doxyfile-gdbserver.in | ||
| fdl.texi | ||
| filter-for-doxygen | ||
| filter-params.pl | ||
| gdb.texinfo | ||
| gpl.texi | ||
| guile.texi | ||
| lpsrc.sed | ||
| Makefile.in | ||
| psrc.sed | ||
| python.texi | ||
| refcard.tex | ||
| stabs.texinfo | ||
| stack_frame.eps | ||
| stack_frame.pdf | ||
| stack_frame.png | ||
| stack_frame.svg | ||
| stack_frame.txt | ||
