diff options
| author | Tom Tromey <tom@tromey.com> | 2023-10-28 11:46:33 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2023-10-30 21:47:36 -0600 |
| commit | 1f9e9ea5b7cd1554db5a5e9da92a6882f1cce40e (patch) | |
| tree | 5461232c2d5f2a3b211f506b826cc861190db590 /gdb/breakpoint.c | |
| parent | a05b22b6c7ff0f48b92086f523f8227d26c84f49 (diff) | |
| download | binutils-1f9e9ea5b7cd1554db5a5e9da92a6882f1cce40e.zip binutils-1f9e9ea5b7cd1554db5a5e9da92a6882f1cce40e.tar.gz binutils-1f9e9ea5b7cd1554db5a5e9da92a6882f1cce40e.tar.bz2 | |
Remove some frame invalidation code
I stumbled across a few spots that mention that a function
"invalidates frame" and also assignments of NULL to a frame_info_ptr.
This code isn't harmful, but is also unnecessary since the
introduction of frame_info_ptr -- nowadays frame invalidations are
handled automatically.
Regression tested on x86-64 Fedora 38.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'gdb/breakpoint.c')
| -rw-r--r-- | gdb/breakpoint.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index 828c99c..fe09dbc 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -10952,9 +10952,6 @@ until_break_command (const char *arg, int from_tty, int anywhere) lj_deleter.emplace (thread); } - /* set_momentary_breakpoint could invalidate FRAME. */ - frame = NULL; - /* If the user told us to continue until a specified location, we don't specify a frame at which we need to stop. Otherwise, specify the selected frame, because we want to stop only at the |