From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20191 invoked by alias); 20 Nov 2015 12:55:14 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 20180 invoked by uid 89); 20 Nov 2015 12:55:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-HELO: usevmg20.ericsson.net Received: from usevmg20.ericsson.net (HELO usevmg20.ericsson.net) (198.24.6.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 20 Nov 2015 12:55:12 +0000 Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 2B.5C.32596.A06BE465; Fri, 20 Nov 2015 06:56:26 +0100 (CET) Received: from [142.133.110.95] (147.117.188.8) by smtp-am.internal.ericsson.com (147.117.188.89) with Microsoft SMTP Server id 14.3.248.2; Fri, 20 Nov 2015 07:55:09 -0500 Subject: Re: Random SIGILL / SIGSEGV on ARMv7 while debugging ? To: Yao Qi References: <564E136E.9090603@ericsson.com> <86poz5yr12.fsf@gmail.com> CC: From: Antoine Tremblay Message-ID: <564F182D.2080801@ericsson.com> Date: Fri, 20 Nov 2015 12:55:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <86poz5yr12.fsf@gmail.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00033.txt.bz2 On 11/20/2015 04:11 AM, Yao Qi wrote: > Antoine Tremblay writes: > > I didn't see any SIGILL/SIGSEGV in my testing. > >> Program received signal SIGILL, Illegal instruction. >> 0xb6fd99e2 in ?? () from target:/lib/ld-linux-armhf.so.3 >> (gdb) FAIL: gdb.trace/change-loc.exp: Can't run to main to check for >> trace support > > Did you see SIGILL with vanilla GDB or GDB with your tracepoint patches? I tested both and the problem was present with vanilla too : gdb --version GNU gdb (Ubuntu 7.9-1ubuntu1) 7.9 > You can turn on debugging output, like "set debug infrun 1" and "set > debug remote 1", and you may find some clues from them. Yes I did that with gdbserver --debug and compared the output from a successful run with a failed run and there was no change. This leads me to suspect the problem is not gdb/gdbserver. Especially since the Pi2 with the same gdb/gdbserver does not have the problem. I'm guessing from your answer you've never seen that in your tests... I think I'll have to work around it by using an other board, I'm looking at the testing the firefly one now : http://en.t-firefly.com/en/firenow/firefly_rk3288/ If ever you have another suggestion of a powerful ARMv7 board with eMMC storage that you know works well it's quite welcome. Thank you, Antoine