From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13208 invoked by alias); 29 Jun 2004 19:18:27 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 13109 invoked from network); 29 Jun 2004 19:18:25 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 29 Jun 2004 19:18:25 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5TJIPe1028956 for ; Tue, 29 Jun 2004 15:18:25 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5TJIN006926; Tue, 29 Jun 2004 15:18:24 -0400 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id i5TJIMvU012598; Tue, 29 Jun 2004 15:18:22 -0400 Received: from toenail (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 27E238002A2; Tue, 29 Jun 2004 15:18:22 -0400 (EDT) Received: from toenail.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by toenail (8.12.10/8.12.5) with ESMTP id i5TJILxj012898; Tue, 29 Jun 2004 15:18:21 -0400 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.12.10/8.12.10/Submit) id i5TJILsf012896; Tue, 29 Jun 2004 15:18:21 -0400 Date: Tue, 29 Jun 2004 19:18:00 -0000 From: "Frank Ch. Eigler" To: Dave Brolley Cc: sid@sources.redhat.com Subject: Re: Misaligned read/write of memory by GDB Message-ID: <20040629191821.GM10148@redhat.com> References: <40E08B13.7000404@redhat.com> <40E0A0B0.3020001@redhat.com> <20040629182721.GK10148@redhat.com> <40E1BEF2.4070401@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1hKfHPzOXWu1rh0v" Content-Disposition: inline In-Reply-To: <40E1BEF2.4070401@redhat.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2004-q2/txt/msg00057.txt.bz2 --1hKfHPzOXWu1rh0v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 758 Hi - > >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=20 > handle misaligned access, either by implementing support, returning=20 > sid::bus::misaligned, or whatever else might be appropriate.=20 How many offenders (that did neither) did you encounter? > 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. [...] True, except that such accesses could originate elsewhere - a simulated CPU, or a gloss component, for example. - FChE --1hKfHPzOXWu1rh0v Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA4cB9VZbdDOm/ZT0RAjbAAJ93DbIsOlTyF98jYqfxc3WfUaNwxgCfY8OE x04OHlcfsCzRWWWplGzJRwo= =5lPj -----END PGP SIGNATURE----- --1hKfHPzOXWu1rh0v--