From: "Korbel, Michal" <Michal.Korbel@intel.com>
To: "'Michael Snyder'" <msnyder@redhat.com>,
"Sarnath K - CTD, Chennai." <k_sarnath@ctd.hcltech.com>
Cc: gdb@sources.redhat.com
Subject: RE: Thread Support for remote debugging
Date: Thu, 31 Jan 2002 23:32:00 -0000 [thread overview]
Message-ID: <413FBB0BA5AED1119122000083234B1A01C74292@alpha.igk.intel.com> (raw)
GDB have remote thread support and works fine with remote multithread
target,
to work with this feature you need have GDBSERVER with remote thread
support.
In the middle of 2001 I was build own version GDBSERVER with remote thread
support (x86-linux target only).
GDB (this version only) have only one restriction, the connection to remote
target can by start only from console window, but after first breakpoints we
can use all GDB features with full mouse support.
----------------------------------------------------------------------------
----------
Michal Korbel - Software engineer
Intel Technology Poland Sp. z o.o.; ul. Slowackiego 173; 80-298 Gdansk
tel. +48 58 34-81-726; fax: +48 58 34-81-505; mobile:+48 603-203-142
----------------------------------------------------------------------------
----------
-----Original Message-----
From: Michael Snyder [mailto:msnyder@redhat.com]
Sent: Thursday, January 31, 2002 9:41 PM
To: Sarnath K - CTD, Chennai.
Cc: gdb@sources.redhat.com
Subject: Re: Thread Support for remote debugging
"Sarnath K - CTD, Chennai." wrote:
>
> Hi,
> I have been browsing the mail archives for
> knowing the current state of thread support
> while doing remote debugging using GDB.
> Although a lot of discussions have happened,
> I am not able to find the current state of work
> in that area.
By "knowing the current state of thread support",
do you mean finding out whether the remote target
supports thread debugging?
If GDB sends the remote target a request that the
remote target does not support, there is a well-defined
way in which the remote target should respond (I believe
it is by sending an empty response).
> I downloaded the latest GDB sources. It doesnt
> support thread commands during remote debugging.
> May I know what is the state of work in this area ?
> Is there any patch available for this ?
I don't understand. GDB implements the remote protocol
for thread support. There are queries defined for asking
the target for the current thread ID, changing the current
thread ID, asking for a list of "live" threads, asking
whether a particular thread is alive...
next reply other threads:[~2002-02-01 7:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 23:32 Korbel, Michal [this message]
2002-02-01 7:45 ` Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2002-02-01 8:13 Korbel, Michal
2002-02-01 8:27 ` Dan Kegel
2002-02-01 9:43 ` Quality Quorum
2002-01-21 22:08 Sarnath K - CTD, Chennai.
2002-01-21 1:11 Sarnath K - CTD, Chennai.
2002-01-21 6:07 ` Daniel Jacobowitz
2002-01-21 7:10 ` Quality Quorum
2002-01-21 8:38 ` Andrew Cagney
2002-01-31 12:47 ` Michael Snyder
2002-01-31 15:12 ` Daniel Jacobowitz
2002-01-31 15:22 ` Quality Quorum
2002-01-31 17:22 ` Daniel Jacobowitz
2002-01-31 19:41 ` Quality Quorum
2002-01-31 19:29 ` Andrew Cagney
2002-01-31 19:44 ` Quality Quorum
2002-01-31 15:41 ` Michael Snyder
2002-01-31 17:18 ` Daniel Jacobowitz
2002-01-31 17:21 ` Michael Snyder
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=413FBB0BA5AED1119122000083234B1A01C74292@alpha.igk.intel.com \
--to=michal.korbel@intel.com \
--cc=gdb@sources.redhat.com \
--cc=k_sarnath@ctd.hcltech.com \
--cc=msnyder@redhat.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