Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulf Carlsson <ulfc@cthulhu.engr.sgi.com>
To: Jeff Harrell <jharrell@ti.com>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu, bbrown@ti.com, mhassler@ti.com,
	vwells@ti.com, kmcdonald@ti.com
Subject: Re: kgdb support
Date: Wed, 24 Nov 1999 14:24:51 -0800	[thread overview]
Message-ID: <19991124142451.H30786@engr.sgi.com> (raw)
In-Reply-To: <383C4F7C.C0C40DE0@ti.com>; from Jeff Harrell on Wed, Nov 24, 1999 at 01:50:04PM -0700

> I am porting the MIPS/Linux version of the Linux kernel to a IDT79S145
> evaluation board.  This board has a IDT64475 (MIPS).  I would like to use a
> standard serial port as a kgdb port.  I will use my other serial port for the
> console port.  Could you provide any additional information regarding the kgdb
> interface?   Is kgdb a standalone application that would need to be built on
> the host to access a target board or is it a patch to the kernel files that
> needs to built into the kernel running on the host?

I think kgdb basically is the same thing as gdb-stubs was, they just renamed it
for some reason. There is a program that comes with gdb-stubs that will let you
drop into kgdb over the serial line if you run it on the target.  You don't need
anything else than gdb to actually run the stuff once the kernel on the target
machine is in the kgdb mode.  If you get a kernel fault, it will automatically
drop into kgdb.  Read the patch and you'll see.

Scott Lurndal is currently working on support for kdb on MIPS, and that will
make things a bit easier when it's working.  Do not exchange kgdb and kdb, they
are two different things :-).

Ulf

  reply	other threads:[~1999-11-24 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24 19:00 kgdb support Jeff Harrell
1999-11-24 19:43 ` Ulf Carlsson
1999-11-24 20:50   ` Jeff Harrell
1999-11-24 22:24     ` Ulf Carlsson [this message]
1999-11-26 10:04       ` X-Window Server Fernando Cela Diaz
1999-11-26 10:04         ` Fernando Cela Diaz

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=19991124142451.H30786@engr.sgi.com \
    --to=ulfc@cthulhu.engr.sgi.com \
    --cc=bbrown@ti.com \
    --cc=jharrell@ti.com \
    --cc=kmcdonald@ti.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=mhassler@ti.com \
    --cc=vwells@ti.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