From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21734 invoked by alias); 23 Jul 2002 14:58:17 -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 21726 invoked from network); 23 Jul 2002 14:58:16 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 23 Jul 2002 14:58:16 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g6NEkfs08729 for ; Tue, 23 Jul 2002 10:46:41 -0400 Received: from deneb.localdomain (msalter.cipe.redhat.com [10.0.0.36]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g6NEwFR02862; Tue, 23 Jul 2002 10:58:15 -0400 Received: (from msalter@localhost) by deneb.localdomain (8.11.6/8.11.6) id g6NEteK28861; Tue, 23 Jul 2002 10:55:40 -0400 Date: Tue, 23 Jul 2002 07:58:00 -0000 Message-Id: <200207231455.g6NEteK28861@deneb.localdomain> From: Mark Salter To: ac131313@ges.redhat.com CC: drow@mvista.com, aminayev@yahoo.com, gdb@sources.redhat.com In-reply-to: <3D3D6CF2.1020708@ges.redhat.com> (message from Andrew Cagney on Tue, 23 Jul 2002 10:49:22 -0400) Subject: Re: gdb-stub question (m packets) References: <20020723080536.90269.qmail@web13506.mail.yahoo.com> <20020723122919.GA6592@nevyn.them.org> <3D3D6CF2.1020708@ges.redhat.com> X-SW-Source: 2002-07/txt/msg00236.txt.bz2 >>>>> Andrew Cagney writes: >> On Tue, Jul 23, 2002 at 01:05:36AM -0700, Alexei Minayev wrote: >> >>> Dear gdb oracles, >>> >>> I'm still fighting with my gdb-h8-stub, and getting funny yet evil errors. >>> The gdb happens to attempt reading a memory location. The content of the >>> memory location is something that starts with 0xE, say 0xE500. >>> The conversation looks kinda like this: >>> >>> m200042,2...Ack >>> Packet received: E500 >>> Unable to access memory location 200042. >>> >>> The gdb understands the numeric hex value of 0xE500 as an error response. >>> So my question would be simple... am I supposed to prefix all my numeric >>> packets with "0x"? Please help, this is confusing... >> >> >> GDBserver uses lowercase hex numbers. That seems to work fine. > Hmm, can someone file a bug report for this: > http://sources.redhat.com/gdb/bugs/ > The error check should be for ``Enn'' (note the three digits - valid > responses would contain two or 4 digits). Still, you have to use lower case. Otherwise a 1 byte read might be mistaken for an error. --Mark