diff options
| author | Tom Tromey <tromey@redhat.com> | 2013-11-22 17:38:44 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2013-11-22 17:38:44 +0000 |
| commit | 6eeee81c8e59511962bdd83df5e7785bfdf871d2 (patch) | |
| tree | 665dbcbe078b8f2ba0878597126ef8eac72d0f66 /gdb/testsuite | |
| parent | 0cb112f7400187275da81a05a9ad0534f1430139 (diff) | |
| download | fsf-binutils-gdb-6eeee81c8e59511962bdd83df5e7785bfdf871d2.zip fsf-binutils-gdb-6eeee81c8e59511962bdd83df5e7785bfdf871d2.tar.gz fsf-binutils-gdb-6eeee81c8e59511962bdd83df5e7785bfdf871d2.tar.bz2 | |
Detect infinite loop in value_fetch_lazy's lval_register handling.
If value_fetch_lazy loops infinitely while unwrapping lval_register
values, it means we either somehow ended up with two frames with the
same ID in the frame chain, or some code is trying to unwind behind
get_prev_frame's back (e.g., a frame unwind sniffer trying to unwind).
In any case, it should always be an internal error to end up in this
situation.
This patch adds a check and throws an internal error if the same frame
is returned.
2013-11-22 Tom Tromey <tromey@redhat.com>
Pedro Alves <palves@redhat.com>
PR backtrace/16155
* value.c (value_fetch_lazy): Internal error if
get_frame_register_value returns the same register.
Diffstat (limited to 'gdb/testsuite')
0 files changed, 0 insertions, 0 deletions