This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: dtable changes causing _very_ slow startup and process-startup headache. [was Re: auto-import ld]
- To: <cygwin-developers at cygwin dot com>
- Subject: Re: dtable changes causing _very_ slow startup and process-startup headache. [was Re: auto-import ld]
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Fri, 8 Jun 2001 08:35:22 +1000
- References: <000901c0ef4e$904cbe50$6e032bb7@BRAMSCHE> <018e01c0ef53$02e833f0$0200a8c0@lifelesswks> <20010607155145.A21540@redhat.com>
----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin-developers@sources.redhat.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