From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 87193 invoked by alias); 29 Mar 2016 23:38:27 -0000 Mailing-List: contact gdb-testers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-testers-owner@sourceware.org Received: (qmail 87176 invoked by uid 89); 29 Mar 2016 23:38:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: kwanyin.sergiodj.net Received: from kwanyin.sergiodj.net (HELO kwanyin.sergiodj.net) (176.31.208.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 29 Mar 2016 23:38:24 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [binutils-gdb] gdb: xtensa: fix frame initialization when PC is invalid From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Message-Id: Date: Wed, 30 Mar 2016 00:05:00 -0000 X-SW-Source: 2016-q1/txt/msg09974.txt.bz2 *** TEST RESULTS FOR COMMIT a08b52b5c45195c0b095215f19422d2ab67a3a8d *** Author: Max Filippov 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 gdb/ * xtensa-tdep.c (xtensa_frame_cache): Change op1 type to LONGEST. Use safe_read_memory_integer instead of read_memory_integer.