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

 > > 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.
 > 
 > I think you mean "child" target?  target exec just reads an exec file
 > on disk.

Well, my changes are in exec.c to exec_ops methods, not to target methods in
inf-child.c.  Then ISTR these get inherited by target methods in inf-ptrace.c

Are you saying that these changes should really be in inf-child.c or just that
I've misunderstood the concept of an exec target?

 > > If all targets could run asynchronously, then it seems that that mode should
 > > be specified at startup:
 > > 
 > >    gdb --async myprog
 > 
 > Can it just be the default, once we get it working?  If I understand
 > correctly, the async-ness of the target should not affect the CLI at
 > all.  It lets you use "continue&" in addition to "continue", but
 > existing commands should keep working as before.
 > 
 > Async mode seems inherently superior.

You're probably right.  I just don't really have the bigger picture to be able
to say that.

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


  reply	other threads:[~2008-03-08 23:09 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
2008-03-08 20:54       ` Daniel Jacobowitz
2008-03-08 23:09         ` Nick Roberts [this message]
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=18387.7279.827881.339251@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --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