FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

gdb: don't set frame id after calling cooked_read_value

Browse source 
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:
Simon Marchi 2023-12-20 18:18:47 +00:00 • committed by Simon Marchi
parent 59b6dbff95
commit 6658f874cf
1 changed files with 0 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
gdb/sentinel-frame.c
View file

@ -54,7 +54,6 @@ sentinel_frame_prev_register (frame_info_ptr this_frame,
gdb_assert (is_sentinel_frame_id (this_frame_id)); gdb_assert (is_sentinel_frame_id (this_frame_id));
value = cache->regcache->cooked_read_value (regnum); value = cache->regcache->cooked_read_value (regnum);
VALUE_NEXT_FRAME_ID (value) = this_frame_id;
return value; return value;
} }