mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-03-01 13:26:47 +08:00
94aedcf7ea
One thing GDB always does when the inferior stops is finding out where it's stopped at, by way of querying the value of the program counter register. To save a packet round trip, the remote target can send the PC value (often alongside other frequently consulted registers such as the stack pointer) in the stop reply packet as an "expedited register". Test that this is actually done for the targets where gdbserver is supposed to. Extend the "maintenance print remote-registers" command output with an "Expedited" column which says "yes" if the register was seen by GDB in the last stop reply packet it received, and is left blank otherwise. Tested for regressions on aarch64-linux-gnu native-extended-remote. The testcase was tested on aarch64-linux-gnu, i686-linux-gnu and x86_64-linux-gnu native-remote and native-extended-remote targets. Reviewed-By: Eli Zaretskii <eliz@gnu.org> Approved-By: Tom Tromey <tom@tromey.com> |
||
|---|---|---|
| .. | ||
| .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 | ||
