From: Pedro Alves <pedro@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sourceware.org
Subject: Re: [non-stop] 00/10 non-stop mode
Date: Wed, 18 Jun 2008 21:37:00 -0000 [thread overview]
Message-ID: <200806182208.35175.pedro@codesourcery.com> (raw)
In-Reply-To: <18521.29761.674435.357159@kahikatea.snap.net.nz>
A Wednesday 18 June 2008 21:46:57, Nick Roberts wrote:
> > > > # Enable the async interface
> > > > maint set linux-async 1
> > >
> > > Why is this still a maintenance command while the others aren't?
> >
> > Because, (if you remember, we've talked about this before)there are
> > issues with async mode that prevent it from being the default (core
> > side, not linux only).
>
> In that case I'm not really sure what you mean by core - non-stop mode
> includes changes to linux-nat.c, so presumably that is linux only.
I don't follow where you're getting at. Async mode requires
target support, but of course there's also code in the core of
GDB to support it. Non-stop mode requires target support, builds
on top of the async mode, and of course needs core support too.
The async limitations are in the core side, and affect any async
target -- currently only linux and remote.
We could merge "maint set linux-async" and "maint set remote-async"
into one global "maint set async", I don't see a problem with that.
--
Pedro Alves
next prev parent reply other threads:[~2008-06-18 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 1:29 Pedro Alves
2008-06-16 7:13 ` Vladimir Prus
2008-06-17 4:24 ` Nick Roberts
2008-06-18 17:32 ` Pedro Alves
2008-06-18 21:36 ` Nick Roberts
2008-06-18 21:37 ` Pedro Alves [this message]
2008-06-19 3:33 ` Nick Roberts
2008-06-19 5:07 ` Pedro Alves
2008-06-19 6:07 ` Nick Roberts
2008-06-19 6:43 ` Pedro Alves
2008-06-19 13:57 ` Marc Khouzam
2008-06-19 16:31 ` Daniel Jacobowitz
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=200806182208.35175.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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