From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15475 invoked by alias); 30 Sep 2003 14:46:39 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 15468 invoked from network); 30 Sep 2003 14:46:39 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 30 Sep 2003 14:46:39 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id BEFFB2B89; Tue, 30 Sep 2003 10:46:38 -0400 (EDT) Message-ID: <3F79974E.4070203@redhat.com> Date: Tue, 30 Sep 2003 14:46:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: LaPonsey Brian-ra4951 Cc: gdb-patches@sources.redhat.com Subject: Re: mcore registers References: <15BB35FC418BD511868500D0B7B916B108A35018@zuk07exm02.sps.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-09/txt/msg00652.txt.bz2 >> Can you post the output from "maint print registers"? If these >> registers are last, the stub can send back a short register >> packet > > > The pc is the last, not cr31 -- Doh! > (gdb) maint print registers > cr31 63 63 252 4 int > pc 64 64 256 4 int > > > >> longer packet back to the stub). It may also be possible to >> run length >> encode (phrase?) the "x" indicating that the the missing >> registers are >> not available. > > > I had planned on eventually implementing the run-length encoding (using the '*' symbol). All of the non-existent registers just get reported as containing zeroes, so RLL would compress this consistently. Maybe it's time to get busy on that. I was hoping for a fix that not only improves performance, but also accurately reflects how the mcore is actually built. Ok. Note that GDB doesn't run length encode. Instead it tries to use the "P" packet. If not already, also look at the "T..." response to things like continue. Andrew