From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8567 invoked by alias); 13 Jun 2003 23:03:42 -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 8281 invoked from network); 13 Jun 2003 23:03:37 -0000 Received: from unknown (HELO planck.amplepower.com) (216.39.162.139) by sources.redhat.com with SMTP; 13 Jun 2003 23:03:37 -0000 Received: from [192.168.8.30] (helo=knuth.amplepower.com ident=roth) by planck.amplepower.com with esmtp (Exim 3.36 #1 (Debian)) id 19QxPH-0002yX-00 for ; Fri, 13 Jun 2003 15:52:27 -0700 Date: Fri, 13 Jun 2003 23:03:00 -0000 From: "Theodore A. Roth" X-X-Sender: roth@knuth.amplepower.com To: gdb@sources.redhat.com Subject: stop reply packets in rsp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-06/txt/msg00269.txt.bz2 Hi, The rsp documentation for the 'T' stop reply packet seems a bit sparse. Is there a minimal set of registers that must be passed to avoid gdb sending a 'g' request while stepping? I assume this is arch specific. For the avr it looks like SP and PC are the minimal set. Does gdb have any preferance as to which reply packets it would like to see? My remote targets seem to do ok with using 'T' replies for 'C', 'c', 'S', and 's' command packets and 'S' replies otherwise. Just curious. Ted Roth