From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g5FKZvnC009707 for ; Sat, 15 Jun 2002 13:35:57 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g5FKZvSh009706 for linux-mips-outgoing; Sat, 15 Jun 2002 13:35:57 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-mips@oss.sgi.com using -f Received: from crack.them.org (mail@crack.them.org [65.125.64.184]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g5FKZpnC009693 for ; Sat, 15 Jun 2002 13:35:52 -0700 Received: from drow by crack.them.org with local (Exim 3.12 #1 (Debian)) id 17JKJc-0004zn-00; Sat, 15 Jun 2002 15:38:32 -0500 Date: Sat, 15 Jun 2002 15:38:31 -0500 From: Daniel Jacobowitz To: Justin Wojdacki Cc: linux-mips@oss.sgi.com Subject: Re: Debugging using GDB and gdbserver Message-ID: <20020615153831.B19123@crack.them.org> References: <3D0B9D14.BFE27F7E@analog.com> <20020615151413.A19123@crack.them.org> <3D0BA3C4.79ED2B5D@analog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3D0BA3C4.79ED2B5D@analog.com>; from justin.wojdacki@analog.com on Sat, Jun 15, 2002 at 01:29:56PM -0700 Sender: owner-linux-mips@oss.sgi.com Precedence: bulk On Sat, Jun 15, 2002 at 01:29:56PM -0700, Justin Wojdacki wrote: > Daniel Jacobowitz wrote: > > > > On Sat, Jun 15, 2002 at 01:01:24PM -0700, Justin Wojdacki wrote: > > > > > > How does GDB work under MIPS Linux? I'm trying to do a bring-up of an > > > embedded device, and it looks like the kernel is missing the code > > > needed to handle software breakpoints. Are there patches that need to > > > be applied to the kernel? > > > > No. If you use a current GDB (I recommend 5.2 or CVS) it should work > > just fine, if you are using a recent kernel (you didn't mention what > > version you were looking at). > > > > -- > > Daniel Jacobowitz Debian GNU/Linux Developer > > MontaVista Software Carnegie Mellon University > > Sorry, I'm using the 2.4.10 kernel and GDB 5.2. What I see happening > is the BREAK 5 instruction from a software breakpoint is hit, and the > kernel loops continuously on that, as it appears to have no way to > deal with that exception. I'm running gdbserver on the MIPS target and > gdb as a cross-debugger on an x86 host (RedHat 7.1). To me, it looks > like when the debugging breakpoint is hit, gdbserver should get > scheduled to run and handle the breakpoint, but instead the child > keep's getting scheduled. Software breakpoints have worked at least as far back as 2.4.2. This most likely means that the exception handling for your board is broken. -- Daniel Jacobowitz Debian GNU/Linux Developer MontaVista Software Carnegie Mellon University