From: Dave Brolley <brolley@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: Misaligned read/write of memory by GDB
Date: Tue, 29 Jun 2004 19:14:00 -0000 [thread overview]
Message-ID: <40E1BEF2.4070401@redhat.com> (raw)
In-Reply-To: <20040629182721.GK10148@redhat.com>
Frank Ch. Eigler wrote:
>OK, but did you consider an alternate of having a memory target that
>is unable to handle an unaligned access return sid::bus::misaligned,
>and then have gdb back down to byte-by-byte access?
>
>
I thought about the possibility of fixing existing memory targets to
handle misaligned access, either by implementing support, returning
sid::bus::misaligned, or whatever else might be appropriate. However it
occurred to me that this would require implementors of all future memory
targets to be aware of potential GDB access of this type. This just
seemed like something that will always work regardless of the
implementation of the downstream memory.
Dave
next prev parent reply other threads:[~2004-06-29 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 21:18 Dave Brolley
2004-06-28 22:50 ` Dave Brolley
2004-06-29 18:27 ` Frank Ch. Eigler
2004-06-29 19:14 ` Dave Brolley [this message]
2004-06-29 19:18 ` Frank Ch. Eigler
2004-06-29 20:40 ` Dave Brolley
2004-07-01 17:02 ` Dave Brolley
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=40E1BEF2.4070401@redhat.com \
--to=brolley@redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).