From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 75562 invoked by alias); 20 Nov 2015 09:11: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 75540 invoked by uid 89); 20 Nov 2015 09:11:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-pa0-f52.google.com Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 20 Nov 2015 09:11:12 +0000 Received: by padhx2 with SMTP id hx2so111073399pad.1 for ; Fri, 20 Nov 2015 01:11:10 -0800 (PST) X-Received: by 10.68.135.132 with SMTP id ps4mr17684688pbb.111.1448010670195; Fri, 20 Nov 2015 01:11:10 -0800 (PST) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by smtp.gmail.com with ESMTPSA id l9sm15515175pbq.43.2015.11.20.01.11.08 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 20 Nov 2015 01:11:09 -0800 (PST) From: Yao Qi To: Antoine Tremblay Cc: Subject: Re: Random SIGILL / SIGSEGV on ARMv7 while debugging ? References: <564E136E.9090603@ericsson.com> Date: Fri, 20 Nov 2015 09:11:00 -0000 In-Reply-To: <564E136E.9090603@ericsson.com> (Antoine Tremblay's message of "Thu, 19 Nov 2015 13:22:38 -0500") Message-ID: <86poz5yr12.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00032.txt.bz2 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? You can turn on debugging output, like "set debug infrun 1" and "set debug remote 1", and you may find some clues from them. --=20 Yao (=E9=BD=90=E5=B0=A7)