From: Daniel Jacobowitz <dan@debian.org>
To: Nathan Field <ndf@ghs.com>
Cc: linux-mips@linux-mips.org
Subject: Re: ptrace induced instruction cache bug?
Date: Tue, 13 Jan 2004 15:58:58 -0500 [thread overview]
Message-ID: <20040113205858.GA17260@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401131029410.1969-100000@zcar.ghs.com>
On Tue, Jan 13, 2004 at 10:35:04AM -0800, Nathan Field wrote:
> > It sounds reasonable. I've encountered this problem in the past also,
> > but never with the Pro 2.1 / MIPS release which is what you're using.
> > I don't see anything obviously wrong with your test code, either.
> So... is there a fix for this?
Usually a missing cache flush, as you surmised :) But I don't know of
any that were missing in that version.
> > Yes, you will need a newer toolchain. Honestly, I'm baffled as to why a
> > Pro 2.1 toolchain was available from our web site at all, unless you got
> > it via an old product subscription... it should have been Pro 3.0, which
> > uses GCC 3.2 and a more recent binutils. But I don't have any control
> > over these things :)
> I downloaded it about 5 days ago from:
> http://www.mvista.com/previewkit/index.html
>
> Could I get a preview kit of your 3.0 release for a Malta 4Kc board?
Let me inquire as to why we're distributing old ones.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-13 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 2:34 ptrace induced instruction cache bug? Nathan Field
2004-01-13 15:01 ` Daniel Jacobowitz
2004-01-13 18:35 ` Nathan Field
2004-01-13 20:58 ` Daniel Jacobowitz [this message]
2004-01-14 23:36 ` Nathan Field
2004-01-15 0:07 ` Jun Sun
2004-01-15 0:22 ` Nathan Field
2004-01-15 0:22 ` Nathan Field
2004-01-15 0:40 ` Jun Sun
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=20040113205858.GA17260@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ndf@ghs.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