From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17690 invoked by alias); 8 Dec 2006 02:35:59 -0000 Received: (qmail 17681 invoked by uid 22791); 8 Dec 2006 02:35:59 -0000 X-Spam-Check-By: sourceware.org Received: from de01egw01.freescale.net (HELO de01egw01.freescale.net) (192.88.165.102) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 08 Dec 2006 02:35:54 +0000 Received: from de01smr02.am.mot.com (de01smr02.freescale.net [10.208.0.151]) by de01egw01.freescale.net (8.12.11/de01egw01) with ESMTP id kB83w96J010901 for ; Thu, 7 Dec 2006 20:58:09 -0700 (MST) Received: from [10.82.23.23] (ld0034-tx32.am.freescale.net [10.82.23.23]) by de01smr02.am.mot.com (8.13.1/8.13.0) with ESMTP id kB82Zo6l027546 for ; Thu, 7 Dec 2006 20:35:51 -0600 (CST) Message-ID: <4578CF86.1080003@freescale.com> Date: Fri, 08 Dec 2006 02:35: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: gdb@sourceware.org Subject: Re: gdb remote serial protocol qC and vCont question Content-Type: text/plain; charset=ISO-8859-1; 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/msg00063.txt.bz2 Daniel, I am using an RSP stub (like gdbserver) built with our ISS model so I am not sure whether I am providing the right information to gdb for the thread switching. The RSP transactions look something like: Received packet: [qC] Sending packet: [QC1] Received packet: [qfThreadInfo] Sending packet: [m1,2,3] Received packet: [qsThreadInfo] Sending packet: [l] .... 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. Really appreciate your help. Thanks, Kishore Daniel Jacobowitz wrote: >On Thu, Dec 07, 2006 at 06:27:25PM -0600, Kishore Paul wrote: > > >>Hi, >> >>Is there a way to communicate thread switching using a reply packet in >>gdb's remote serial protocol. >> >>I notice the qC packet sent only at the begining and so later when a >>thread switch happens in the target a vCont packet is sent with the old >>active thread Id. >> >> > >GDB is supposed to send vCont for the correct thread; if it doesn't, >something's wrong on the GDB side. > > >