gdb: xtensa: fix frame initialization when PC is invalid
authorMax Filippov <jcmvbkbc@gmail.com>
Sun, 27 Mar 2016 17:45:54 +0000 (20:45 +0300)
committerMax Filippov <jcmvbkbc@gmail.com>
Tue, 29 Mar 2016 23:17:24 +0000 (02:17 +0300)
commita08b52b5c45195c0b095215f19422d2ab67a3a8d
tree4d6d903cebc3f9f321160b29fbd304bbbb241d93
parentc37c0ba69b670f0994b53078abdb07737f816a5a
gdb: xtensa: fix frame initialization when PC is invalid

When gdb is used on core dump and PC is not pointing to a readable
memory read_memory_integer call in the xtensa_frame_cache throws an
error, making register inspection/backtracing impossible in that thread.

Use safe_read_memory_integer instead.

2016-03-29  Max Filippov  <jcmvbkbc@gmail.com>
gdb/
* xtensa-tdep.c (xtensa_frame_cache): Change op1 type to LONGEST.
Use safe_read_memory_integer instead of read_memory_integer.
gdb/ChangeLog
gdb/xtensa-tdep.c