From: Scott Anderson <scott_anderson@mvista.com>
To: "Justin (Gus) Hurwitz" <ghurwitz@dyndns.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Seg fault whenever NIP=c0006000
Date: Wed, 18 Jul 2001 10:35:27 -0700 [thread overview]
Message-ID: <3B55C8DF.5D8C0EF2@mvista.com> (raw)
In-Reply-To: Pine.LNX.3.95.1010718035902.16243A-100000@november.bhjjh.erols.com
"Justin (Gus) Hurwitz" wrote:
> So- it appears that avoiding address 0xc0006000, and only that address, is
> necessary for my kernel (true, I haven't tested every other byte of
> memory, but the kernel does appear stable). Anyone have ideas a to what
> could cause this?
Sorry if this is an obvious question, but is there any chance that there
is some code somewhere that is either intentionally or unintentionally
setting up a hardware breakpoint?
Scott Anderson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-07-18 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 8:11 Seg fault whenever NIP=c0006000 Justin (Gus) Hurwitz
2001-07-18 17:35 ` Scott Anderson [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=3B55C8DF.5D8C0EF2@mvista.com \
--to=scott_anderson@mvista.com \
--cc=ghurwitz@dyndns.com \
--cc=linuxppc-embedded@lists.linuxppc.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.