public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] gdb: xtensa: fix frame initialization when PC is invalid
@ 2016-03-30  0:05 sergiodj+buildbot
  2016-03-30  0:06 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: sergiodj+buildbot @ 2016-03-30  0:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a08b52b5c45195c0b095215f19422d2ab67a3a8d ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: a08b52b5c45195c0b095215f19422d2ab67a3a8d

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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-03-30  3:05 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-30  0:05 [binutils-gdb] gdb: xtensa: fix frame initialization when PC is invalid sergiodj+buildbot
2016-03-30  0:06 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot
2016-03-30  0:52 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-03-30  3:05 ` Failures on Debian-i686, " sergiodj+buildbot
2016-03-30  3:12 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-30  3:48 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).