This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v3] gdb: xtensa: fix frame initialization when PC is invalid
- From: Pedro Alves <palves at redhat dot com>
- To: Max Filippov <jcmvbkbc at gmail dot com>, gdb-patches at sourceware dot org
- Cc: Maxim Grigoriev <maxim2405 at gmail dot com>, Woody LaRue <larue at cadence dot com>, Marc Gauthier <marc at cadence dot com>
- Date: Wed, 30 Mar 2016 00:07:43 +0100
- Subject: Re: [PATCH v3] gdb: xtensa: fix frame initialization when PC is invalid
- Authentication-results: sourceware.org; auth=none
- References: <1459281476-28077-1-git-send-email-jcmvbkbc at gmail dot com>
On 03/29/2016 08:57 PM, Max Filippov wrote:
> 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.
OK.
Thanks,
Pedro Alves