Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] catch syscall -- try 4 -- Architecture-independent part
Date: Mon, 09 Mar 2009 18:31:00 -0000	[thread overview]
Message-ID: <200903091831.43521.pedro@codesourcery.com> (raw)
In-Reply-To: <20090309131856.GA16796@caradoc.them.org>

On Monday 09 March 2009 13:18:56, Daniel Jacobowitz wrote:
> > > Not sure that the flag exists any more, but you're trying to avoid it
> > > when called by startup_inferior.  I suppose you could use the
> > > inferior_created observer (not new_inferior!  The distinction is not
> > > too clear in the manual but that one is too early).  The problem is,
> > > again, that this flag needs to be per-inferior.
> > > 
> > > Pedro, any thoughts?

Makes sense to me.

Alternatively, can we use inf->stop_soon != STOP_QUIETLY for this?

This flag is already per-inferior.  The only small problem is, since
startup_inferior was rewritten to not use wait_for_inferior, we're not
setting stop_soon = STOP_QUIETLY while in there anymore.  We could
bring that bit back again.  Just something like setting stop_soon = STOP_QUIETLY
on entry to startup_inferior, and clear it on exit to NO_STOP_QUIETLY on
exit.

-- 
Pedro Alves


  parent reply	other threads:[~2009-03-09 18:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  0:31 Sérgio Durigan Júnior
2009-01-26  0:51 ` Pedro Alves
2009-01-26  4:56   ` Sérgio Durigan Júnior
2009-01-26 17:04     ` Sérgio Durigan Júnior
2009-02-01 19:33       ` Daniel Jacobowitz
2009-02-25 21:44         ` Sérgio Durigan Júnior
2009-02-28  0:44           ` Daniel Jacobowitz
2009-03-08 18:16             ` Sérgio Durigan Júnior
2009-03-09 13:19               ` Daniel Jacobowitz
2009-03-09 14:09                 ` Sérgio Durigan Júnior
2009-03-09 18:39                   ` Pedro Alves
2009-03-09 18:56                     ` Daniel Jacobowitz
2009-03-09 18:31                 ` Pedro Alves [this message]
2009-03-29 21:16             ` Sérgio Durigan Júnior
2009-03-31 16:39               ` Daniel Jacobowitz
2009-04-09 19:29                 ` Sérgio Durigan Júnior
2009-04-09 19:36                   ` Daniel Jacobowitz
2009-04-09 20:21                     ` Sérgio Durigan Júnior
2009-04-15 23:12                 ` Sérgio Durigan Júnior

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=200903091831.43521.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@linux.vnet.ibm.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