From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-33082-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 7697 invoked by alias); 26 Sep 2008 08:35:42 -0000
Received: (qmail 7376 invoked by uid 22791); 26 Sep 2008 08:35:40 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.net.t-labs.tu-berlin.de (HELO mail.net.t-labs.tu-berlin.de) (130.149.220.252)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 Sep 2008 08:34:44 +0000
Received: from [130.149.220.22] (ara.net.t-labs.tu-berlin.de [130.149.220.22]) 	by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id 84DBC700A276; 	Fri, 26 Sep 2008 10:34:41 +0200 (CEST)
Message-ID: <48DC9EA0.4040509@net.t-labs.tu-berlin.de>
Date: Fri, 26 Sep 2008 08:35:00 -0000
From: =?ISO-8859-1?Q?Harald_Schi=F6berg?=  <harald@net.t-labs.tu-berlin.de>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Shane Volpe <shanevolpe@gmail.com>
CC: gdb@sourceware.org
Subject: Re: gdb backtrace after SIGILL on Xscale (ARM)
References: <8c7950360809231027m64797d8dwfa60be3c164fd80c@mail.gmail.com>
In-Reply-To: <8c7950360809231027m64797d8dwfa60be3c164fd80c@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-09/txt/msg00134.txt.bz2


This sounds like an EABI vs. OABI issue. see this thread:

http://sourceware.org/ml/gdb/2008-01/msg00032.html

harald


Shane Volpe wrote:
> I'm trying to perform a backtrace using gdb after a SIGILL event on an
> Xscale (ARM) target device.  In order to simplify the issue I have
> wrote a small program (http://en.wikipedia.org/wiki/SIGILL) whose only
> purpose is to cause a SIGINT.
> 
> The code is:
> int main()
> {
>     unsigned char insn[4] = { 0xff, 0xff, 0xff, 0xff };
>     void (*function)() = (void (*)()) insn;
>     function();
> }
> 
> I compiled it as follows:
> gcc -o sigill sigill.c
> 
> I then run it on my host machine 'Linux, Arch: x86"
> 
> gdb /home/sigill
> (gdb) run
> Starting program: /home/sigill
> 
> Program received signal SIGILL, Illegal instruction.
> 0xbf81d400 in ?? ()
> (gdb) bt
> #0  0xbf81d400 in ?? ()
> #1  0x08048363 in main ()
> 
> 
> Every thing work as expected, I got a backtrace showing me the correct steps.
> 
> I then compiled the program for my target system "Linux, Arch: Xscale (ARM)"
> I ran the app and got the following:
> 
>  /home/sigill
> BFD: /lib/.debug/ld-2.5.so: warning: sh_link not set for section `.ARM.exidx'
> BFD: /lib/.debug/libc-2.5.so: warning: sh_link not set for section `.ARM.exidx'
> 
> Program received signal SIGILL, Illegal instruction.
> 0xbea7fc44 in ?? ()
> (gdb) bt
> #0  0xbea7fc44 in ?? ()
> (gdb)
> 
> There is NO real information provided in the backtrace, why is this,
> what might I be doing wrong?
> 
> Regards,
> Shane


-- 
Harald Schiöberg
Technische Universität Berlin | T-Laboratories | FG INET
www: http://www.net.t-labs.tu-berlin.de
Phone: +49-(0)30-8353-58476 | Fax: +49-(0)391 534 783 47