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)
commit6658f874cf7b521bf2ce431fcf31cc89aebc7009
treedb8d90a77e915e56caeee6a4e01ae26f7dc451c2
parent59b6dbff95a72896b12510309b12e431075f1e63
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
gdb/sentinel-frame.c