[PATCH 1/9] gdb: don't set frame id after calling cooked_read_value

Simon Marchi
2023-12-21T19:17:33Z

I don't think that setting the next frame id is needed there, all code
paths in cooked_read_value do set it properly, AFAIK.

Change-Id: Idb9d9e6f89c2c95c5ebfeec2a63fde89ed84cf3d
---
gdb/sentinel-frame.c | 1 -
1 file changed, 1 deletion(-)

diff --git a/gdb/sentinel-frame.c b/gdb/sentinel-frame.c
index 3e5b9be2edf6..9a9e4c29198e 100644
--- a/gdb/sentinel-frame.c
+++ b/gdb/sentinel-frame.c
@@ -54,7 +54,6 @@ sentinel_frame_prev_register (frame_info_ptr this_frame,
gdb_assert (is_sentinel_frame_id (this_frame_id));

value = cache->regcache->cooked_read_value (regnum);
- VALUE_NEXT_FRAME_ID (value) = this_frame_id;

return value;
}
--
2.43.0