dtable changes causing _very_ slow startup and process-startup headache. [was Re: auto-import ld]

Christopher Faylor cgf@redhat.com
Thu Jun 7 17:30:00 GMT 2001


On Fri, Jun 08, 2001 at 08:53:38AM +1000, Robert Collins wrote:
>
>----- Original Message -----
>From: "Christopher Faylor" <cgf@redhat.com>
>To: <cygwin-developers@cygwin.com>
>Sent: Friday, June 08, 2001 8:52 AM
>Subject: Re: dtable changes causing _very_ slow startup and
>process-startup headache. [was Re: auto-import ld]
>
>
>>On Fri, Jun 08, 2001 at 08:35:22AM +1000, Robert Collins wrote:
>>>----- Original Message -----
>>>From: "Christopher Faylor" <cgf@redhat.com>
>>>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.
>>
>>Set a breakpoint in the appropriate routine.
>
>
>I tried that :[.
>
>$ gdb -nw df.exe (gdb) dll cygwin1.dll (gdb) break dtable::extend
>Cannot access memory at address 0x61006618

I don't know why gdb works this way but you should be able
to set a breakpoint on the line number inside of dtable::extend.
You can't set a breakpoint on the function itself before the
program runs.

cgf



More information about the Cygwin-developers mailing list