From: Keith Seitz <keiths@redhat.com>
To: Ruppert <ru@swb.siemens.de>
Cc: insight@sources.redhat.com
Subject: Re: memory window: bug wrt endianness
Date: Mon, 04 Nov 2002 10:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0211041034460.2435-100000@lindt.uglyboxes.com> (raw)
In-Reply-To: <200211041641.gA4GfFD07597@fiji.swb.siemens.de>
On Mon, 4 Nov 2002, Ruppert wrote:
> I think I found a bug with the implementation of the memory
> window in insight-5.1: values written to memory from the memory
> window are written with the wrong endianness (at least in the "word"
> representation of the window).
Have you tried this in a newer version (like CVS head)? I seem to
recollect some changes in the memory window wrt endianness problems being
checked in...
If the problem still exists, we'll take it from there.
Keith
next prev parent reply other threads:[~2002-11-04 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 8:41 Ruppert
2002-11-04 10:38 ` Keith Seitz [this message]
2002-11-04 10:44 ` Martin M. Hunt
2002-11-05 3:44 Ruppert
2002-11-05 3:56 Ruppert
2002-11-05 4:42 Ruppert
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=Pine.LNX.4.44.0211041034460.2435-100000@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=ru@swb.siemens.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).