diff options
| author | Hannes Domani <ssbssa@yahoo.de> | 2020-12-18 18:23:41 +0100 |
|---|---|---|
| committer | Hannes Domani <ssbssa@yahoo.de> | 2021-02-07 19:08:23 +0100 |
| commit | 83962f8340726373e0d174dcf688818eb7faea6b (patch) | |
| tree | 78a229831c029e1721224978f48066bf1515a308 /gdb/tui | |
| parent | de8d4203109ae04c05a716c1afb2d5a487e9b1fe (diff) | |
| download | binutils-83962f8340726373e0d174dcf688818eb7faea6b.zip binutils-83962f8340726373e0d174dcf688818eb7faea6b.tar.gz binutils-83962f8340726373e0d174dcf688818eb7faea6b.tar.bz2 | |
Also compare frame_id_is_next in frapy_richcompare
The last frame in a corrupt stack stores the frame_id of the next frame,
so these two frames currently compare as equal.
So if you have a backtrace where the oldest frame is corrupt, this happens:
(gdb) py
>f = gdb.selected_frame()
>while f.older():
> f = f.older()
>print(f == f.newer())
>end
True
With this change, that same example returns False.
gdb/ChangeLog:
2021-02-07 Hannes Domani <ssbssa@yahoo.de>
* python/py-frame.c (frapy_richcompare): Compare frame_id_is_next.
Diffstat (limited to 'gdb/tui')
0 files changed, 0 insertions, 0 deletions