Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
		gdb-patches@sources.redhat.com
Subject: Re: [RFA] Async mode fixes.
Date: Fri, 07 Mar 2008 22:33:00 -0000	[thread overview]
Message-ID: <20080307223247.GA12001@caradoc.them.org> (raw)
In-Reply-To: <18385.48967.964309.898509@kahikatea.snap.net.nz>

Hi Nick, thanks for looking at this.  I was hoping you would.

On Sat, Mar 08, 2008 at 11:18:47AM +1300, Nick Roberts wrote:
> Like my patch, IMO this one looks a bit like a dog's breakfast.  It's got some
> good ideas, though, and has certainly increased my understanding of the
> asynchronous code.  Perhaps a combination of the two patches would create
> something useful.

As I understand it, it already is combined - I know Vladimir started
with a copy of your most recent async patch.  I haven't looked at his
patch yet but it may need to be broken down into some pieces.
 
> It may reduce the failures, but I suspect that's partly because it's not really
> running asynchronously.  I don't understand how it really could without adding
> another file handler for inferior events.  That doesn't mean it can't, just
> that I don't understand how it could.

Vladimir, what target were you using to test - was it "target async"?
If so, there's already a file handler relevant to inferior events;
"target async" uses the remote protocol to talk to gdbserver, so it
receives events every time there's a byte on the TCP socket.

> I think sync mode is also needed for command files.

Shouldn't you be able to use async operations from a command file?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-07 22:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  7:27 Vladimir Prus
2008-03-07 22:19 ` Nick Roberts
2008-03-07 22:33   ` Daniel Jacobowitz [this message]
2008-03-08  8:16     ` Vladimir Prus
2008-03-08  8:59   ` Vladimir Prus
2008-03-08 20:36     ` Nick Roberts
2008-03-08 20:54       ` Daniel Jacobowitz
2008-03-08 23:09         ` Nick Roberts
2008-03-09  0:01           ` Daniel Jacobowitz
2008-03-10  7:58       ` Vladimir Prus
2008-03-10  9:12         ` Nick Roberts
2008-03-10 10:02           ` Vladimir Prus
2008-03-10 22:06             ` Nick Roberts
2008-03-14 18:26 ` Daniel Jacobowitz
2008-03-14 18:58   ` Vladimir Prus
2008-03-17 14:11 ` [commit] Fix compile error (Re: [RFA] Async mode fixes.) Ulrich Weigand
2008-03-17 14:17   ` 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=20080307223247.GA12001@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.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