Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jie Zhang <jie.zhang@analog.com>
To: "nagaraju.m" <nagaraju.m@redpinesignals.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	  Paul Pluzhnikov <ppluzhnikov@google.com>,
	 "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: processor threads
Date: Wed, 21 Oct 2009 08:58:00 -0000	[thread overview]
Message-ID: <4ADEA476.7000409@analog.com> (raw)
In-Reply-To: <4ADE9F3E.1040200@redpinesignals.com>

nagaraju.m wrote:
> Hi Michael,
> 
>    I mean to say that we are having 4 hardware threads.  Our company has 
> its own processor on which we will be working.         The processor 
> currently we are working has 4 threads in it.
> 
>    Each thread has it own set of registers (ex: program counter).
> 
>    Currently the GDB which we are using is supporting only single thread 
> (ex: thread 0).
>    Now we trying to use GDB for remaining threads.
> 
>    My Question is does GDB handles hardware threads??
> 
Maybe GDB threads support will work for you. Our JTAG GDB stub supports 
dual-core Blackfin processor. The stub treats each core as one thread. 
In gdb, you can use thread commands for cores.


Jie


  reply	other threads:[~2009-10-21  6:05 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 [this message]
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

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=4ADEA476.7000409@analog.com \
    --to=jie.zhang@analog.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=nagaraju.m@redpinesignals.com \
    --cc=ppluzhnikov@google.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