All of lore.kernel.org
 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:16:05 -0700	[thread overview]
Message-ID: <3D0BBCA5.5A0D722A@analog.com> (raw)
In-Reply-To: 20020615153831.B19123@crack.them.org

Daniel Jacobowitz wrote:
> 
> 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.
> 

Sorry, originally misinterpretted your use of "board" as referring to
the board itself, and perhaps PMON (I've found a number of references
online to GDB talking to PMON, but not much else). 

So what I've found by looking at other board-specific code revolves
around GDB talking to an in-kernel stub via the serial port. As the
board I'm working with has an unreliable serial port (and some
incarnations don't even have that), what about ethernet-based
debugging? Is that do-able, say via putDebugChar() (although I suspect
this poses an initialization problem)? 

Thanks for the info so far. 

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

  parent reply	other threads:[~2002-06-15 22:13 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 [this message]
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=3D0BBCA5.5A0D722A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.