From: Brian Heilig <bheilig@etinternational.com>
To: gdb <gdb@sourceware.org>
Subject: Problems with non-stop - Porting gdb to Cyclops64
Date: Fri, 06 Aug 2010 18:39:00 -0000 [thread overview]
Message-ID: <1281119953.1560.96.camel@random> (raw)
In-Reply-To: <201008051519.39349.pedro@codesourcery.com>
Dear list,
I am having trouble making gdb happy in non-stop mode. When I connect to
my target in non-stop mode gdb queries for the list of active threads.
It then sends a stop request for the first thread in the list,
"vCont;t:1".
The documentation for this feature states: "A stop reply should be
generated for any affected thread not already stopped. When a thread is
stopped by means of a `t' action, the corresponding stop reply should
indicate that the thread has stopped with signal `0', regardless of
whether the target uses some other signal as an implementation detail."
So I send back my stop response: "$T00;thread:1;". gdb responds with
"Stopping Thread 1 failed: T00;thread:1;" and disconnects from the
target.
I tried this same test on my Linux desktop using version 7.1-ubuntu and
received a very different response.
Server: gdbserver :0 a.out
Client: gdb a.out
Set non-stop on the client and then connect with "target
remote :<port>".
Client sends "vCont;t:<thread>"
Server responds with "$OK". The gdb prompt never appears and (as far as
I can tell) nothing can be done with the gdb session.
Am I doing something wrong?
Thanks,
Brian
next prev parent reply other threads:[~2010-08-06 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 17:13 Brian Heilig
2010-07-30 17:26 ` Michael Snyder
2010-07-30 18:53 ` Brian Heilig
2010-07-30 18:57 ` Michael Snyder
2010-07-30 20:28 ` Brian Heilig
2010-07-30 22:54 ` Michael Snyder
2010-07-30 23:18 ` Pedro Alves
2010-08-02 13:25 ` Brian Heilig
2010-08-02 13:35 ` Pedro Alves
2010-08-03 16:52 ` Brian Heilig
2010-08-05 13:56 ` Brian Heilig
2010-08-05 14:19 ` Pedro Alves
2010-08-06 18:39 ` Brian Heilig [this message]
2010-08-30 19:44 ` Cyclops64 Multi-Process Brian Heilig
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=1281119953.1560.96.camel@random \
--to=bheilig@etinternational.com \
--cc=gdb@sourceware.org \
/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).