Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: linux native async mode support
Date: Sat, 15 Mar 2008 03:11:00 -0000	[thread overview]
Message-ID: <20080315031043.GB29828@caradoc.them.org> (raw)
In-Reply-To: <200803150157.47855.pedro@codesourcery.com>

On Sat, Mar 15, 2008 at 01:57:47AM +0000, Pedro Alves wrote:
> we get to the point where the non-async code path is not needed anymore,
> we can drop a bunch of support code.  That's doesn't seem likelly to
> happen anytime soon in the common code, but it can be done target by
> target.  Linux native and target (extended-)remote are the first
> candidates.

Exactly.  Pedro and I both know how to do this on native Windows, and
can test there.  A similar version to the GNU/Linux code will work on
other ptrace targets (not exactly the same, I think, but pretty
close).  Ttrace may need something different, but I'm sure it's
possible.  I suspect that procfs will be easy, for someone more
familiar with it.  And the various remote targets are all similar
in this regard.

In short, I don't think it will be very difficult to get rid of
synchronous target_wait.  It will probably take a year from when
we get GNU/Linux and remote working, while we round up people familiar
with all the various supported interfaces, and some of them we'll
probably have to guess.  But I think we can do it.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-15  3:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  8:11 Pedro Alves
2008-03-14 21:17 ` Daniel Jacobowitz
2008-03-17 16:05   ` Pedro Alves
2008-03-17 22:05     ` Daniel Jacobowitz
2008-03-18 23:27       ` Pedro Alves
2008-03-18 23:58         ` Daniel Jacobowitz
2008-03-21 15:55         ` Daniel Jacobowitz
2008-03-21 17:19           ` Pedro Alves
2008-03-28 14:48             ` Maciej W. Rozycki
2008-03-28 16:07               ` Pedro Alves
2008-03-28 16:13                 ` Daniel Jacobowitz
2008-03-28 16:40                   ` Pedro Alves
2008-03-18  0:06     ` Nick Roberts
2008-03-18 23:28       ` Pedro Alves
2008-03-19  3:59         ` Nick Roberts
2008-03-19 16:25           ` Luis Machado
2008-03-19 23:19             ` Pedro Alves
2008-03-19 23:26               ` Pedro Alves
2008-03-20  1:58               ` Nick Roberts
2008-03-21 15:47                 ` Daniel Jacobowitz
2008-03-21 15:49       ` Daniel Jacobowitz
2008-03-21 23:02         ` Nick Roberts
2008-03-22  1:25           ` Daniel Jacobowitz
2008-03-22 22:06             ` Nick Roberts
2008-04-01 14:00               ` Daniel Jacobowitz
2008-04-01 15:17               ` Vladimir Prus
2008-04-01 20:09                 ` Nick Roberts
2008-04-04 12:34                   ` Vladimir Prus
2008-04-05 17:20                     ` Nick Roberts
2008-04-05 22:07                       ` Vladimir Prus
2008-04-07  0:06                         ` Nick Roberts
2008-04-07  2:33                         ` Nick Roberts
2008-03-18  2:47     ` Nick Roberts
2008-03-14 23:10 ` Nick Roberts
2008-03-15  1:58   ` Pedro Alves
2008-03-15  3:11     ` Daniel Jacobowitz [this message]
2008-03-17 23:41     ` Nick Roberts

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=20080315031043.GB29828@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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