aboutsummaryrefslogtreecommitdiff
path: root/libctf
diff options
context:
space:
mode:
authorKevin Buettner <kevinb@redhat.com>2025-02-24 13:04:00 -0700
committerKevin Buettner <kevinb@redhat.com>2025-02-24 13:05:02 -0700
commit04bfaa910acb40412d35ef622a02c3a27ace1991 (patch)
tree434b9c32de8e3d5c8d27763cecde27e1a67acd50 /libctf
parent431b369e1cb963b221345991a25f901a0b58d91a (diff)
downloadbinutils-04bfaa910acb40412d35ef622a02c3a27ace1991.zip
binutils-04bfaa910acb40412d35ef622a02c3a27ace1991.tar.gz
binutils-04bfaa910acb40412d35ef622a02c3a27ace1991.tar.bz2
Use ui_out for "info checkpoints"
In his review of my recent checkpoint work (commit e5501dd4321), Andrew Burgess suggested that I use GDB's structured table generation mechanism for the "info checkpoints" command. This patch does that. Andrew also recommended using print_stack_frame() for the "Frame" column. I tried this, but ran into some problems, which are described in a comment in the code. I got it to mostly work, except for the case when the current/active fork is running. Switching context away from and then back to a running fork doesn't work. It could, perhaps, be made to work, but I'm not convinced that the checkpoint facility is important enough to expend the effort for this case. So, instead, I simply adapted the existing checkpoint frame printing code to use the ui_out machinery instead of gdb_printf. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'libctf')
0 files changed, 0 insertions, 0 deletions