Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Use multi-arch'd START_INFERIOR_TRAPS_EXPECTED on Alpha target
Date: Wed, 24 Apr 2002 18:04:00 -0000	[thread overview]
Message-ID: <20020424180352.B26223@dr-evil.shagadelic.org> (raw)
In-Reply-To: <3CC74887.2070401@cygnus.com>; from ac131313@cygnus.com on Wed, Apr 24, 2002 at 08:06:31PM -0400

On Wed, Apr 24, 2002 at 08:06:31PM -0400, Andrew Cagney wrote:

 >    #define STARTUP_WITH_SHELL 1
 > - #define START_INFERIOR_TRAPS_EXPECTED (STARTUP_WITH_SHELL + 1)
 > 
 > Does STARTUP_WITH_SHELL need to be multi-arched?
 > 
 > I'm wondering if it would be better to make it a variable (``set 
 > startup-with-shell <boolean>'').  Looking at its uses it appears that 
 > fork-child.c:startup_inferior() would still work (if it did previously).

Hm.  Actually, it occurs to me that this is more like what we want, but
not quite.  What we really want is:

	STARTUP_WITH_SHELL_ADDS_TRAPS

So, then we get:

#define START_INFERIOR_TRAPS_EXPECTED \
  (startup_with_shell ? (STARTUP_WITH_SHELL_ADDS_TRAPS + 1) : 1)

I.e. the issue is really how many extra traps the shell adds.

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>


  parent reply	other threads:[~2002-04-25  1:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 18:15 Jason R Thorpe
2002-04-24 17:06 ` Andrew Cagney
2002-04-24 17:45   ` Jason R Thorpe
2002-04-24 18:04   ` Jason R Thorpe [this message]
2002-04-24 19:30     ` Andrew Cagney
2002-04-25 13:03   ` Daniel Jacobowitz
2002-04-25 14:29     ` Michael Snyder
2002-04-25 15:00       ` 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=20020424180352.B26223@dr-evil.shagadelic.org \
    --to=thorpej@wasabisystems.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.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