gdb: don't set frame id after calling cooked_read_value
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
This commit is contained in:
committed by
Simon Marchi
parent
59b6dbff95
commit
6658f874cf
@@ -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;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user