From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-40649-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 2074 invoked by alias); 3 Apr 2012 07:28:51 -0000
Received: (qmail 2047 invoked by uid 22791); 3 Apr 2012 07:28:49 -0000
X-SWARE-Spam-Status: No, hits=1.5 required=5.0	tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_BRBL_LASTEXT,RCVD_IN_HOSTKARMA_YE,RCVD_IN_NJABL_RELAY,RDNS_NONE
X-Spam-Check-By: sourceware.org
Received: from Unknown (HELO new.toad.com) (209.237.225.253)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Apr 2012 07:28:28 +0000
Received: from new.toad.com (localhost.localdomain [127.0.0.1])	by new.toad.com (8.12.9/8.12.9) with ESMTP id q337SMWD018124	for <gdb@sourceware.org>; Tue, 3 Apr 2012 00:28:22 -0700
Message-Id: <201204030728.q337SMWD018124@new.toad.com>
To: gdb@sourceware.org
Subject: Re: PR13901
In-reply-to: <4F79AFF4.9000704@redhat.com>
References: <20120330134210.GA7869@bromo.med.uc.edu> <AA980E80-C63F-490E-B804-73B1CC9047ED@adacore.com> <14D51CD4-4990-4B11-952C-64EB8F791306@adacore.com> <4F79AFF4.9000704@redhat.com>
Comments: In-reply-to Pedro Alves <palves@redhat.com>   message dated "Mon, 02 Apr 2012 14:56:04 +0100."
Date: Tue, 03 Apr 2012 07:28:00 -0000
From: John Gilmore <gnu@toad.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2012-04/txt/msg00027.txt.bz2

> If we can't skip darwin_set_sstep for all continues that are not single-steps,
> we could at least skip those while starting up (when continuing the shell
> until we see enough execs).  That'd suggest a new flag like
> darwin-nat.h:struct private_inferior->starting_up, set and cleared in
> darwin_create_inferior, and then making darwin_resume_thread do ...

When I was maintaining GDB (many years ago), touching *anything* in
the state machine that figured out what to do next when the inferior
stopped was guaranteed to produce several bugs for every fix.

In the changes we made, I tried to reduce that tendency, and make
the code more modular and less fragile.  Today, "just" adding a new
flag for this may be as simple as you hope.

	John Gilmore