From: Jie Zhang <jzhang918@gmail.com>
To: "nagaraju.m" <nagaraju.m@redpinesignals.com>
Cc: Michael Snyder <msnyder@vmware.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: processor threads
Date: Sat, 24 Oct 2009 16:03:00 -0000 [thread overview]
Message-ID: <6f48278f0910240803yc5ea1a1m51d6aec0dd7c6c43@mail.gmail.com> (raw)
In-Reply-To: <4AE00144.5020201@redpinesignals.com>
On Thu, Oct 22, 2009 at 2:52 PM, nagaraju.m
<nagaraju.m@redpinesignals.com> wrote:
> Can you please forward me any links on how to implement threads support to a
> specific target.
>
Besides the links Michael pointed out, you can take gdbproxy as an
example of implementation.
http://blackfin.uclinux.org/gf/project/toolchain/scmsvn/trunk/gdbproxy
Hope this also helps.
Jie
prev parent reply other threads:[~2009-10-24 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 7:35 nagaraju.m
2009-10-20 17:55 ` Paul Pluzhnikov
2009-10-20 17:58 ` Michael Snyder
2009-10-21 6:05 ` nagaraju.m
2009-10-21 8:58 ` Jie Zhang
2009-10-21 14:34 ` Michael Snyder
2009-10-22 15:23 ` nagaraju.m
2009-10-22 20:19 ` Michael Snyder
2009-10-24 16:03 ` Jie Zhang [this message]
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=6f48278f0910240803yc5ea1a1m51d6aec0dd7c6c43@mail.gmail.com \
--to=jzhang918@gmail.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=nagaraju.m@redpinesignals.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