diff options
author | Guinevere Larsen <guinevere@redhat.com> | 2024-03-14 16:14:25 +0100 |
---|---|---|
committer | Guinevere Larsen <guinevere@redhat.com> | 2025-01-17 11:49:16 -0300 |
commit | 3919cf8a704138e4f2dd79c66e33a62087180f1f (patch) | |
tree | 3de1b90bfe0308f1fab7ddd24ca00fc6fb1f57af /gdb/doc | |
parent | 7965f0a0031c360ef9ce8c4ff01f422dd43b99b1 (diff) | |
download | binutils-3919cf8a704138e4f2dd79c66e33a62087180f1f.zip binutils-3919cf8a704138e4f2dd79c66e33a62087180f1f.tar.gz binutils-3919cf8a704138e4f2dd79c66e33a62087180f1f.tar.bz2 |
gdb: make gdbarch store a vector of frame unwinders
Before this commit, all frame unwinders would be stored in the obstack
of a gdbarch and accessed by using the registry system. This made for
unwieldy code, and unnecessarily complex logic in the frame_unwinder
implementation, along with making frame_unwind structs be unable to have
non-trivial destructors.
Seeing as a future patch of this series wants to refactor the
frame_unwind struct to use inheritance, and we'd like to not restrict
the future derived classes on what destructors are allowed. In
preparation for that change, this commit changes the registry in gdbarch
to instead store an std::vector, which doesn't require using an obstack
and doesn't rely on a linked list.
There should be no user-visible changes.
Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Approved-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'gdb/doc')
0 files changed, 0 insertions, 0 deletions