Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <009901c0efa2$23f65320$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
References: <000901c0ef4e$904cbe50$6e032bb7 AT BRAMSCHE> <018e01c0ef53$02e833f0$0200a8c0 AT lifelesswks> <20010607155145 DOT A21540 AT redhat DOT com>
Subject: Re: dtable changes causing _very_ slow startup and process-startup headache. [was Re: auto-import ld]
Date: Fri, 8 Jun 2001 08:35:22 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 07 Jun 2001 22:26:20.0385 (UTC) FILETIME=[E0550D10:01C0EFA0]

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
To: <cygwin-developers AT sources DOT redhat DOT com>
Sent: Friday, June 08, 2001 5:51 AM
Subject: Re: dtable changes causing _very_ slow startup and
process-startup headache. [was Re: auto-import ld]


>
> What clues are you hoping for that wouldn't be immediately apparent
from
> running gdb on this?  If there is a substantial delay, it should be
really
> easy to figure out where this is.

There are no clues immediately apparent _after_ running GDB on this.
Should != what I experienced.

Clues_p (If it was a known HEAD issue, or if it sparked a memory for
you!?)

How do you get gdb to stop in cygwin1.dll before main() is reached? The
delay occurs during dll initialisation AFAICT, and I haven't managed to
find out how to stop that early on.

Likewise the linked exe stackdumps under bash/sh but not under cmd.exe.

Rob