From: Piet/Pete Delaney <piet@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] use of gdb for ia64 kernel debug
Date: Tue, 30 Apr 2002 18:25:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905543@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905532@msgid-missing>
On Tue, Apr 30, 2002 at 02:02:10PM +0100, Doug Rabson wrote:
> On Mon, 29 Apr 2002, David Mosberger wrote:
>
> > >>>>> On Fri, 26 Apr 2002 17:33:37 -0500, Ray Bryant <raybry@engr.sgi.com> said:
> >
> > Ray> Is is possible to use an IA32 system as a gdb host and run a
> > Ray> remote debugging session on an IA64 box (e. g. a Big Sur)?
> >
> > You need a gdb stub in the kernel for doing that. I seem to recall
> > someone wrote such a stub for FreeBSD (or was it NetBSD)? If so, you
> > could use that as a starting point.
>
> There is a 'stub of a stub' in the FreeBSD-current kernel but it certainly
> isn't functional on ia64. I don't yet use gdb for kernel debugging on
> FreeBSD.
I notced it don't look compete; I got the impression from "David O'Brien" <obrien@FreeBSD.org>
that it's working; perhaps they just haven't checked it all in yet:
"I don't know about ia64, but all the hard core sparc64 developers are
using serial console and perfer it."
Often the trap code can take a lot of time to get right; this is the primary
reason I thought it might be easier to use skdb and leave the ia64 low level
details to kdb. Once working I was hoping we could add an option to kdb to
provide checksums on consile I/O like the stub protocol uses.
-piet
prev parent reply other threads:[~2002-04-30 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 22:33 [Linux-ia64] use of gdb for ia64 kernel debug Ray Bryant
2002-04-29 18:36 ` David Mosberger
2002-04-29 19:22 ` Piet/Pete Delaney
2002-04-30 13:02 ` Doug Rabson
2002-04-30 18:25 ` Piet/Pete Delaney [this message]
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=marc-linux-ia64-105590701905543@msgid-missing \
--to=piet@sgi.com \
--cc=linux-ia64@vger.kernel.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.