From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27658 invoked by alias); 28 Feb 2017 10:21:40 -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 27643 invoked by uid 89); 28 Feb 2017 10:21:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS,URIBL_RED autolearn=no version=3.3.2 spammy=H*i:sk:1fb132a, Hx-languages-length:955, H*f:sk:1fb132a X-HELO: mail-wr0-f193.google.com Received: from mail-wr0-f193.google.com (HELO mail-wr0-f193.google.com) (209.85.128.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 28 Feb 2017 10:21:38 +0000 Received: by mail-wr0-f193.google.com with SMTP id u48so1023137wrc.1 for ; Tue, 28 Feb 2017 02:21:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=0kUqvVlkYCZveg2snqPcTdY1V6KvDChLSDO2ijBTZ7s=; b=WcTqIKJ1ruMFReDEfJU52M3RVN6UpCzarUiwNdI/KuDQMj1h0PKpXXcIzOzDa7z3nh tIlTwE8Fk1eWdIrFdHbZ/mkCCifWo1jj1vLtKmT5+QySTqaG+d6VjZ4U4O8syhalH2kt gs4EcD5knoLpcQLohr5riPKBMz92u4VfYPPpYEmHMpbIyuy9VLaD7kNi1rZPhALSsEzp NkeQLdMQg82f7n3wljlq0G1rP+ZDy0WypKd5dRNsBTP1ncCnOIXA6uXOkxkB15h6i3Yp PU5GhMh9izzxoDumTOlSHPKZHNo/tOFEoLDT+3rkA8oYZ5p3+vVx75ZcAVjHLJousWgh TbNQ== X-Gm-Message-State: AMke39lHWFqfGU12g2m5uKemG5vB5FwAAM46cZmc67w1CAzNzTwpbm33KTE15VZYJzNR1A== X-Received: by 10.223.172.77 with SMTP id v71mr1763030wrc.131.1488277296265; Tue, 28 Feb 2017 02:21:36 -0800 (PST) Received: from E107787-LIN ([194.214.185.158]) by smtp.gmail.com with ESMTPSA id w97sm349440wrc.20.2017.02.28.02.21.35 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 28 Feb 2017 02:21:35 -0800 (PST) From: Yao Qi To: Luis Machado Cc: Steve Ellcey , gdb Subject: Re: Question about backtraces through signal handlers for aarch64 ILP32 support References: <1488241574.2866.227.camel@caviumnetworks.com> <1fb132ae-4230-2ae1-ad57-6ca51b1c8d97@codesourcery.com> Date: Tue, 28 Feb 2017 10:21:00 -0000 In-Reply-To: <1fb132ae-4230-2ae1-ad57-6ca51b1c8d97@codesourcery.com> (Luis Machado's message of "Mon, 27 Feb 2017 18:36:16 -0600") Message-ID: <868toqsjj0.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: 2017-02/txt/msg00059.txt.bz2 Luis Machado writes: >> Normal backtraces seem to be working fine, the majority of ILP32 failures >> I get in gdb.base (that don't also happen in LP64 mode) are tests with '= sig' >> in their name like sigstep. >> >> Any ideas on where to look or what to look for? > > That extra frame indicates gdb is getting confused when extracting > register state from the signal frame and creates a spurious frame at > 0x0. Maybe gdb is finding a frame pointer that points to 0x0 and > should instead point to 0x00400740 (main)? Tracking that down may help > figure it out. I think Luis is right. From your log, I can see that sigframe is found, and the right unwinder is used, but it gets the wrong value when it unwinds stack. Probably, you need to look at aarch64-linux-tdep.c:aarch64_linux_sigframe_init and some macros defines above. --=20 Yao (=E9=BD=90=E5=B0=A7)