Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Justin Wojdacki <justin.wojdacki@analog.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: Debugging using GDB and gdbserver
Date: Sat, 15 Jun 2002 15:40:08 -0700	[thread overview]
Message-ID: <3D0BC248.16CB7EC2@analog.com> (raw)
In-Reply-To: 20020615172645.A19472@crack.them.org

Daniel Jacobowitz wrote:
>
> Wait, wait.  What are you trying to do?  Originally you were talking
> about userspace debugging via gdbserver.  Now you're talking about
> kernel debugging via kgdb.  They're separate (and coexisting can cause
> problems if you are not careful with your exception handlers; I do not
> remember when my patches to make that work went into the tree, or if
> someone else did it).
> 
> gdbserver can just use TCP.
> 
> --
> Daniel Jacobowitz                           Debian GNU/Linux Developer
> MontaVista Software                         Carnegie Mellon University

Sorry for the confusion. I've been discussing userspace debugging via
gdbserver the entire time. However, I've noticed that gdbserver
doesn't seem to be fully functional because the kernel doesn't seem to
be handling the "BREAK 5" instruction correctly. You mentioned
problems with board exception handling and I looked at the ddb series
board support code. In there, I found handling for software
breakpoints, and got the impression from the code that it was a
general debugging interface, not just for kernel debugging. Again,
sorry for the confusion.

As it stands right now, when I get hit a "BREAK 5" instruction,
gdbserver never get's a chance to handle it, as the kernel keeps
scheduling the child process I'm trying to debug, and hitting the
"BREAK 5" instruction over and over again. What I can't seem to find
out is how gdbserver is supposed to get scheduled again. 

-- 
-------------------------------------------------
Justin Wojdacki        
justin.wojdacki@analog.com         (408) 350-5032
Communications Processors Group -- Analog Devices

  reply	other threads:[~2002-06-15 22:37 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
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 [this message]
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=3D0BC248.16CB7EC2@analog.com \
    --to=justin.wojdacki@analog.com \
    --cc=dmj+@andrew.cmu.edu \
    --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