Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Justin Wojdacki <justin.wojdacki@analog.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Debugging using GDB and gdbserver
Date: Sat, 15 Jun 2002 15:38:31 -0500	[thread overview]
Message-ID: <20020615153831.B19123@crack.them.org> (raw)
In-Reply-To: <3D0BA3C4.79ED2B5D@analog.com>; from justin.wojdacki@analog.com on Sat, Jun 15, 2002 at 01:29:56PM -0700

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

  reply	other threads:[~2002-06-15 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 20:01 Debugging using GDB and gdbserver Justin Wojdacki
2002-06-15 20:14 ` Daniel Jacobowitz
2002-06-15 20:29   ` Justin Wojdacki
2002-06-15 20:38     ` Daniel Jacobowitz [this message]
2002-06-15 20:45       ` Justin Wojdacki
2002-06-15 22:16       ` Justin Wojdacki
2002-06-15 22:26         ` Daniel Jacobowitz
2002-06-15 22:40           ` Justin Wojdacki
2002-06-15 23:03             ` Daniel Jacobowitz
2002-06-15 23:05               ` Justin Wojdacki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020615153831.B19123@crack.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=justin.wojdacki@analog.com \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox