Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Async mode fixes.
Date: Sat, 08 Mar 2008 20:36:00 -0000	[thread overview]
Message-ID: <18386.63679.965070.279756@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200803081158.40723.vladimir@codesourcery.com>

 > Well, "target async" exists and has existed for a long time. I presume that
 > when it was added, it fully worked. However, as it was not routinely tested,
 > it has regressed to its current state.

I think the asynchronous mode wasn't completed and that it only ever worked for
remote targets.  I'm starting to understand your patch now and see that your
changes just make the asynchronous mode of remote targets work - and that's a
sensible place to start.

 >...
 > > You don't appear to have changed that.  This is where I have issue with the
 > > current `async' mode: it doesn't appear to use this continuation.
 > 
 > Are you sure? I get the following with my patch:
 > 
 > 	(gdb)
 > 	-interpreter-exec console continue
 > 	~"Continuing.\n"
 > 	^running
 > 	*stopped,reason="breakpoint-hit",bkptno="1",thread-id="1",.....

I've not tested your patch, just looked at it.  This doesn't work in the
current code but I see now, as you say, that it's because target_executing is
not reset to 0, not because the continuation isn't called.

You say:

> Yes. Nick patch has two bits:
> 1. Linux native async mode (which Pedro is looking at as we speak)
> 2. Core async mode changes.

It really has three bits:

1. Core async mode changes.
2. Exec async mode changes.
3. Linux native async mode.

I think the command "target async" is a bit misleading and it should really be
called "target remote-async" (I'm not really suggesting changing it).

My changes aren't just for Linux, but an exec target.  I mean native debugging
(I think) with just one implementation - linux.  It sounds like I'm inflating
what I've done but other native targets can presumably be adapted to make use
of the changes in inf-ptrace.c, exec.c etc.

If all targets could run asynchronously, then it seems that that mode should
be specified at startup:

   gdb --async myprog

in which case

  (gdb) target remote host:2222

would do what

  (gdb) target async host:2222

currently does and

  (gdb) run

would run the native applications asynchronously.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-03-08 20:36 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
2008-03-08  8:16     ` Vladimir Prus
2008-03-08  8:59   ` Vladimir Prus
2008-03-08 20:36     ` Nick Roberts [this message]
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=18386.63679.965070.279756@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --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