From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26260 invoked by alias); 2 May 2002 21:13:40 -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 26201 invoked from network); 2 May 2002 21:13:38 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 2 May 2002 21:13:38 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 173NtZ-0006hK-00 for ; Thu, 02 May 2002 17:13:45 -0400 Date: Thu, 02 May 2002 14:13:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: RFC: Two small remote protocol extensions Message-ID: <20020502211345.GC25410@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <3CD15D5A.7020308@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2002-05/txt/msg00024.txt.bz2 On Thu, May 02, 2002 at 04:13:20PM -0400, Quality Quorum wrote: > There some more annoying things in gdb protocol which require careful > consideration: I know. I intend to clean up the spec documentation in a couple of weeks, if I have time. > 4. exact meaning of Hg - last time I checked it was related to registers Yes, although it's unclear; for instance Txxxx;thread:N changes general_thread. > 5. exact meaning of Hc - last time I check it did not mean anything > because gdb itself was not able to support per thread breakpoints It's used for scheduler locking. GDB does support per thread breakpoints (somewhat), but that's not related to Hc... -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer