From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19097 invoked by alias); 8 Dec 2006 22:00:39 -0000 Received: (qmail 19086 invoked by uid 22791); 8 Dec 2006 22:00:35 -0000 X-Spam-Check-By: sourceware.org Received: from de01egw02.freescale.net (HELO de01egw02.freescale.net) (192.88.165.103) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 08 Dec 2006 22:00:27 +0000 Received: from de01smr01.freescale.net (de01smr01.freescale.net [10.208.0.31]) by de01egw02.freescale.net (8.12.11/de01egw02) with ESMTP id kB8MEjh8008922; Fri, 8 Dec 2006 15:14:45 -0700 (MST) Received: from [10.82.23.23] (ld0034-tx32.am.freescale.net [10.82.23.23]) by de01smr01.freescale.net (8.13.1/8.13.0) with ESMTP id kB8M0FaR012287; Fri, 8 Dec 2006 16:00:15 -0600 (CST) Message-ID: <4579E06F.9040205@freescale.com> Date: Fri, 08 Dec 2006 22:00:00 -0000 From: Kishore Paul User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.2) Gecko/20040803 MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb@sourceware.org Subject: Re: gdb remote serial protocol qC and vCont question References: <4578B16D.3090404@freescale.com> <20061208013236.GA18882@nevyn.them.org> <4578CDF7.2000909@freescale.com> <20061208032856.GA21855@nevyn.them.org> In-Reply-To: <20061208032856.GA21855@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: 2006-12/txt/msg00068.txt.bz2 Daniel, The T packet works and I am seeing the threads switching now. Thanks, Kishore Daniel Jacobowitz wrote: >On Thu, Dec 07, 2006 at 08:29:11PM -0600, Kishore Paul wrote: > > >>Received packet: [vCont;s:1;c] -------------> (1) >>.... >> < thread switch happens to 2 > >>.... >> >>Received packet: [vCont;s:1;c] -------------> (2)* >> >> >>Between the first and second vCont packet the thread-id changes from 1 >>to 2 but this information is somehow not getting communicated to gdb. >>The intent of the second vCont is to do a step for thread 2 and c for >>all other threads. >> >> > >How do you expect GDB to know this if you aren't telling it? It can't >guess! > >The thing you're missing is the 'T' response and the "thread:" item in >it. > > >