From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1739 invoked by alias); 16 Jun 2008 01:44:29 -0000 Received: (qmail 1730 invoked by uid 22791); 16 Jun 2008 01:44:29 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Jun 2008 01:44:04 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 8B0C49840B; Mon, 16 Jun 2008 01:44:02 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 2EC3F98011; Mon, 16 Jun 2008 01:44:02 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1K83lJ-0002fQ-Dh; Sun, 15 Jun 2008 21:44:01 -0400 Date: Mon, 16 Jun 2008 01:44:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: John Carter , gdb@sourceware.org Subject: Re: What does gdb stub need for thread aware debugging on embedded system? Message-ID: <20080616014401.GA10193@caradoc.them.org> Mail-Followup-To: Michael Snyder , John Carter , gdb@sourceware.org References: <1213575599.3601.898.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1213575599.3601.898.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00156.txt.bz2 On Sun, Jun 15, 2008 at 05:19:59PM -0700, Michael Snyder wrote: > At the time that that code was written, threads were very far from > the minds of people who wrote remote gdb stubs! Yeah. While sparc-stub.c is a valid example, keep in mind that it is a very old one. There's been a tremendous amount of change in the remote protocol since then, including in the threads area (see e.g. the description of vCont in the remote protocol documentation, which is in the GDB manual). -- Daniel Jacobowitz CodeSourcery