From: Kent Borg <kentborg@borg.org>
To: Mark Pilon <mpilon@midrivers.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: gdb / gdbserver part 2
Date: Thu, 24 Jan 2002 09:04:51 -0500 [thread overview]
Message-ID: <20020124090451.A22567@borg.org> (raw)
In-Reply-To: <3C4EEFAA.1108DF1B@midrivers.com>; from mpilon@midrivers.com on Wed, Jan 23, 2002 at 10:15:22AM -0700
On Wed, Jan 23, 2002 at 10:15:22AM -0700, Mark Pilon wrote:
> I've made some progress but have hit a strange snag and would
> appreciate any context / suggestions you might have.
I don't know if the symptoms you describe fit, be we had a related
problem recently.
Our boot ROM was not clearing the debug hardware at boot. The ptrace
trap handling code was then tripping over spurious bits in whatever
the status word is called.
-kb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-01-24 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 17:15 gdb / gdbserver part 2 Mark Pilon
2002-01-24 14:04 ` Kent Borg [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=20020124090451.A22567@borg.org \
--to=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mpilon@midrivers.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;
as well as URLs for NNTP newsgroup(s).