From: Daniel Jacobowitz <drow@false.org>
To: Kishore Paul <kishorep@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: gdb remote serial protocol qC and vCont question
Date: Fri, 08 Dec 2006 01:32:00 -0000 [thread overview]
Message-ID: <20061208013236.GA18882@nevyn.them.org> (raw)
In-Reply-To: <4578B16D.3090404@freescale.com>
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-08 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 0:27 Kishore Paul
2006-12-08 1:32 ` Daniel Jacobowitz [this message]
[not found] ` <4578CDF7.2000909@freescale.com>
2006-12-08 3:29 ` Daniel Jacobowitz
2006-12-08 22:00 ` Kishore Paul
2006-12-08 2:35 Kishore Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061208013236.GA18882@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=kishorep@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox