diff options
author | Andrew Burgess <aburgess@redhat.com> | 2022-04-21 11:16:18 +0100 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2022-04-21 11:49:30 +0100 |
commit | 3ab22dba1b7ef469b743e5606731ebc1169fbafa (patch) | |
tree | 45f4510fd829034f56f783ef45fe7d7e17c2fede /gdb/trad-frame.c | |
parent | f0072f79e12d88ca361de04a52434430a10c5f0e (diff) | |
download | gdb-3ab22dba1b7ef469b743e5606731ebc1169fbafa.zip gdb-3ab22dba1b7ef469b743e5606731ebc1169fbafa.tar.gz gdb-3ab22dba1b7ef469b743e5606731ebc1169fbafa.tar.bz2 |
gdb: fix 'remote show FOO-packet' aliases
The following behaviour was observed in GDB:
(gdb) show remote X-packet
Support for the `p' packet is auto-detected, currently unknown.
Note the message mentions the 'p' packet. This is a regression since
this commit:
commit 8579fd136a614985bd27f20539c7bb7c5a51287d
Date: Mon Nov 8 14:58:46 2021 +0000
gdb/gdbsupport: make xstrprintf and xstrvprintf return a unique_ptr
Before this commit the behaviour was:
(gdb) show remote X-packet
Support for the `X' packet is auto-detected, currently unknown.
The problem was caused by a failed attempt to ensure that some
allocated strings were deleted when GDB exits. The code in the above
commit attempted to make use of 'static' to solve this problem,
however, the solution was just wrong.
In this new commit I instead allocate a static vector into which all
the allocated strings are stored, this ensures the strings are
released when GDB exits (which makes output from tools like valgrind
cleaner), but each string within the vector can be unique, which fixes
the regression.
Diffstat (limited to 'gdb/trad-frame.c')
0 files changed, 0 insertions, 0 deletions