From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30540 invoked by alias); 18 Nov 2001 23:43:15 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 30526 invoked from network); 18 Nov 2001 23:43:15 -0000 Date: Sat, 10 Nov 2001 11:10:00 -0000 From: Cristiano Ligieri Pereira To: Ben Elliston cc: sid@sources.redhat.com Subject: Re: Running the hello.c example In-Reply-To: <15352.16731.174898.123650@scooby.brisbane.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-q4/txt/msg00015.txt.bz2 Hi Ben, That's the trace I got: 0xd2a8: BL 0x876c: MOV_REG_IMM_SHIFT 0x8770: STMDB_WB 0x8774: SUB_IMM 0x8778: MOV_REG_IMM_SHIFT 0x877c: BL 0x8758: MOV_REG_IMM_SHIFT 0x875c: STMDB_WB 0x8760: SUB_IMM 0x8764: SWI Fault (software, 0x69) pc=0x8764 and this is the piece of the original code where the error is happening: 00008758 <_swiwrite>: 8758: e1a0c00d mov ip, sp 875c: e92dd800 stmdb sp!, {fp, ip, lr, pc} 8760: e24cb004 sub fp, ip, #4 ; 0x4 8764: ef000069 swi 0x00000069 8768: e91ba800 ldmdb fp, {fp, sp, pc} SWI is software interrupt, right? Looks like I'm trying to execution function 0x69 that doesn't exist? is this right? Why would this happen? This is such a simple example. And one more question..., which configuration is being used (besides ARM processor) once I haven't specified any configuration file, let alone created some configuration. thanks, Cristiano. ------------------------------------------------------------ Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira On Mon, 19 Nov 2001, Ben Elliston wrote: > >>>>> "Cristiano" == Cristiano Ligieri Pereira writes: > > Cristiano> When I start arm-elf-sid, though, I get the following error: > > Cristiano> % arm-elf-sid hello.x > Cristiano> Fault (software, 0x69) pc=0x8764 > > You might want to use arm-elf-sid --trace-semantics hello.x. Armed > (no pun intended) with a disassembly of your program, you should be > able to see what's going on. > > Ben >