public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kleck <jim.kleck@NetergyNet.COM>
To: insight@sourceware.cygnus.com
Subject: thread support
Date: Wed, 28 Mar 2001 08:28:00 -0000	[thread overview]
Message-ID: <3AC211CE.644D6BAC@netergynet.com> (raw)

We are working on an embedded target to add gdb support. We are using
insight 5.0. Everyting is going well except for one area: thread support.
I have been unable to figure out exactly what RSP packets are needed
and how to interpret them and their contents. In particular, it seems
that the gdb ThreadId is 1-based (when I return thrId = 0 for the "qC"
pkt, insight/gdb gets confused), whereas thread ids internal to the
target are 0-based. I have tried (external thrid = internal thrid + 1)
and this helped considerably but there are still problems. are there any
docs regarding this?

JimK


             reply	other threads:[~2001-03-28  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-28  8:28 Jim Kleck [this message]
2001-03-28  8:52 ` Fernando Nasser
  -- strict thread matches above, loose matches on Subject: below --
1999-08-04 15:24 Thread support Judy Anderson
1999-08-10  1:53 ` Jim Blandy

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=3AC211CE.644D6BAC@netergynet.com \
    --to=jim.kleck@netergynet.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).