From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27019 invoked by alias); 9 Apr 2002 02:48:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26954 invoked from network); 9 Apr 2002 02:48:23 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 9 Apr 2002 02:48:23 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 01C303EF8; Mon, 8 Apr 2002 22:48:23 -0400 (EDT) Message-ID: <3CB25677.1040902@cygnus.com> Date: Mon, 08 Apr 2002 19:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020328 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Bartlett Cc: gdb@sources.redhat.com Subject: Re: gdbserver, remote serial protocol and endian issues References: <005701c1deea$d9cd52b0$300e81a4@bri.st.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00111.txt.bz2 > In our case, the registers are not byte addressable >> and need to be written variously as 8, 16 and 32 bit >> quantities. Again, remote serial protocol does not >> provide for access size definition. I assume you mean something like a memory read at &foo only works if done as a 16 bit operation by the remote target. > This one is definitely a shortcoming in the remote protocol. Proposals for an extension to the protocol that implement this have been posted (search for e-mail from jtc). The memory attribute framework was introduced in preparation for this. enjoy, Andrew