From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8401 invoked by alias); 2 Jun 2002 16:51:35 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 8383 invoked from network); 2 Jun 2002 16:51:31 -0000 Received: from unknown (HELO branoic) (66.19.120.59) by sources.redhat.com with SMTP; 2 Jun 2002 16:51:31 -0000 Received: from drow by branoic with local (Exim 3.35 #1 (Debian)) id 17EYZV-0002Bs-00; Sun, 02 Jun 2002 12:51:13 -0400 Date: Sun, 02 Jun 2002 09:51:00 -0000 From: Daniel Jacobowitz To: Eero Tamminen Cc: gdb@sources.redhat.com Subject: Re: GDB 5.2 undefined instruction problem on arm9 Message-ID: <20020602165111.GA8408@branoic.them.org> Mail-Followup-To: Eero Tamminen , gdb@sources.redhat.com References: <200206021202.g52C2WA00692@posti.pp.htv.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206021202.g52C2WA00692@posti.pp.htv.fi> User-Agent: Mutt/1.3.28i X-SW-Source: 2002-06/txt/msg00008.txt.bz2 On Sun, Jun 02, 2002 at 03:15:28PM +0300, Eero Tamminen wrote: > Hi, > > I'm trying to cross-compile gdb 5.2 (released version, not CVS) for arm. > > Compilation succeeds and gdb works on the arm (it runs and can display > it's help, load program etc), but when I try to debug programs with it, > the debugged program will stop between '_start' and 'main' with SIGILL > and gdb says "undefined instruction". When I run the program > _without_ gdb, the program works OK. > > This is my first try at trying to compile gdb myself, so I'm wondering > whether the problem is in how I've configured gdb, my cross-compilation > environment, gdb arm support, kernel debugging (ptrace?) support > or what. > > Arm version is arm9, I'm configuring gdb with '--target=arm > --host=arm" and I'm using a cross-compiled glibc with which I link > gdb statically (using the -static linker flag). Cross-compiler is > gcc 2.95.3. The problem is how you configured gdb. Use --target=arm-linux instead; Linux and hardware monitors signal breakpoints in different ways. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer