From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13517 invoked by alias); 23 Jul 2002 14:49:23 -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 13498 invoked from network); 23 Jul 2002 14:49:22 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 23 Jul 2002 14:49:22 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6AB253CED; Tue, 23 Jul 2002 10:49:22 -0400 (EDT) Message-ID: <3D3D6CF2.1020708@ges.redhat.com> Date: Tue, 23 Jul 2002 07:49:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020708 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz , Alexei Minayev Cc: gdb@sources.redhat.com Subject: Re: gdb-stub question (m packets) References: <20020723080536.90269.qmail@web13506.mail.yahoo.com> <20020723122919.GA6592@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg00235.txt.bz2 > 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). Andrew