From: Daniel Jacobowitz <dan@debian.org>
To: Mark and Janice Juszczec <juszczec@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: cross debugging r3912 cpu with gdb
Date: Mon, 8 Dec 2003 10:39:33 -0500 [thread overview]
Message-ID: <20031208153932.GA27486@nevyn.them.org> (raw)
In-Reply-To: <LAW10-F527kP31wEf2X00017cd3@hotmail.com>
On Mon, Dec 08, 2003 at 12:48:44PM +0000, Mark and Janice Juszczec wrote:
>
> Daniel
>
> >
> >Then what ARE you using on the target?
> >
>
> I have a kernel, busybox (for init and sh) and kaffe+associated files.
> These have all been cross compiled from i386 for mipsel-linux using gcc
> (2.95 or 3.0).
>
> >You have to connect to some particular debug stub. That determines
> >what protocol to use.
> >
>
>
> I wanted to test starting the whole thing up and connecting with gdb before
> trying to actually debug anything. So, I haven't begun to worry about
> debug stubs.
GDB has to connect _to_ something :) If you don't have a stub, nothing
on your target speaks the GDB protocol.
> Frankly, I'm confused as to where they'd go. It seems to me I want to let
> the kernel start up on the pda and then use gdb to tell it to start running
> kaffe. If that's true, I need debug stubs in kaffe. Am I completely wrong
> with this idea?
Yes. I recommend you read the GDB manual, on the section describing
gdbserver. GDB doesn't connect to the kernel at all, you start a
gdbserver process on the target with the path to kaffe.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-08 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 12:48 cross debugging r3912 cpu with gdb Mark and Janice Juszczec
2003-12-08 15:39 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 0:02 Mark and Janice Juszczec
2003-12-08 0:02 ` Mark and Janice Juszczec
2003-12-08 3:10 ` Daniel Jacobowitz
2003-12-07 22:28 Mark and Janice Juszczec
2003-12-07 22:54 ` Daniel Jacobowitz
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=20031208153932.GA27486@nevyn.them.org \
--to=dan@debian.org \
--cc=juszczec@hotmail.com \
--cc=linux-mips@linux-mips.org \
/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.