gdb: don't set frame id after calling cooked_read_value
authorSimon Marchi <simon.marchi@efficios.com>
Wed, 20 Dec 2023 18:18:47 +0000 (18:18 +0000)
committerSimon Marchi <simon.marchi@polymtl.ca>
Sun, 24 Dec 2023 14:02:08 +0000 (09:02 -0500)
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

index 3e5b9be..9a9e4c2 100644 (file)
@@ -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;
 }