aboutsummaryrefslogtreecommitdiff
path: root/gdb/source-cache.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-06-22 12:23:53 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-10-02 11:57:30 +0100
commit21a52f7d827dab6bf14f81f478e1f9c7bdc7f218 (patch)
tree2f7693de7a3b14790964cdd96d20de704309259f /gdb/source-cache.c
parentf7052ade774e66cdbca9e3e4839ea747a88af85b (diff)
downloadgdb-21a52f7d827dab6bf14f81f478e1f9c7bdc7f218.zip
gdb-21a52f7d827dab6bf14f81f478e1f9c7bdc7f218.tar.gz
gdb-21a52f7d827dab6bf14f81f478e1f9c7bdc7f218.tar.bz2
gdb/testsuite: new test for -data-disassemble opcodes format
Add another test for the output of MI command -data-disassemble. The new check validates the format of the 'opcodes' field, specifically, this test checks that the field contains a series of bytes, separated by a single space. We also check that the bytes are in the correct order, that is, the first byte is from the lowest address, and subsequent bytes are from increasing addresses. The motivation for this test (besides more tests being generally good) is that I plan to make changes to how opcode bytes are displayed in the disassembler output, and I want to ensure that I don't break any existing MI behaviour. There should be no user visible changes to GDB after this commit.
Diffstat (limited to 'gdb/source-cache.c')
0 files changed, 0 insertions, 0 deletions