From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: "Marc Khouzam" <marc.khouzam@ericsson.com>
Subject: Re: Does HEAD support non-stop with 'gdbserver --multi' on Linux?
Date: Thu, 30 Apr 2009 20:20:00 -0000 [thread overview]
Message-ID: <200904302049.49881.pedro@codesourcery.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA075CAD65@ecamlmw720.eamcs.ericsson.se>
Hi Marc,
On Thursday 30 April 2009 20:39:47, Marc Khouzam wrote:
> In the last couple months there has been a set of patches about
> non-stop/multi-process
> for gdbserver and GDB for Linux from Pedro. Sadly, I wasn't able to
> keep track of what went
> in and all the functionality they supported.
>
> I'm trying HEAD with:
> - gdbserver --multi
Note that --multi is not about multi-process in the same sense you're
talking about. It is a preexisting option that means that gdbserver
will stay persistent even when the inferior exits. It also enables
starting up gdbserver without giving it a process to start with.
You'll need to connect with "target extended-remote" in that case.
The gdbserver multiprocess support is in head already, but needs
more GDB side work to be useable.
> - non-stop for a multi-threaded app
> - on Linux
>
> Is that supported yet?
> Because I'm not getting the correct list of threads (only in the
> non-stop case).
What exactly are you seeing? I just run a few non-stop test
(mi-nonstop.exp, mi-nsintrall.exp and ns-nsmoribund.exp tests)
against linux x86-64 gdbserver head, and they passed cleanly for
me, so *something* is working. :-)
--
Pedro Alves
next prev parent reply other threads:[~2009-04-30 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 19:49 Marc Khouzam
2009-04-30 20:20 ` Pedro Alves [this message]
2009-04-30 20:55 ` Marc Khouzam
[not found] ` <200904302245.11843.pedro@codesourcery.com>
2009-05-01 18:40 ` Marc Khouzam
2009-05-12 15:23 ` Marc Khouzam
2009-05-12 15:58 ` Pedro Alves
2009-05-12 16:23 ` Marc Khouzam
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=200904302049.49881.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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