Debugging under SMP problem

Chris Faylor
Thu Jun 29 15:23:00 GMT 2000

There is only one "cygwin component" that has a version number of 1.1.2, and
that's the Cygwin DLL.

I regret that I don't understand why you're seeing this problem if you are
truly using that DLL.  The only advice I can offer is to make absolutely sure
that some older DLL is not in your path.  "cygcheck -r -s -v" should tell you
if that is the case.


On Fri, Jun 30, 2000 at 01:12:54AM +0300, Michael V. Nikolaev wrote:
>What Cygwin components do you mean? I installed all software from (directory "latest"). I also tried to solve the problem with cygwin1.dll from the CVS snapshot (22-jun-2000). Unfortunately with no success. By the way my previous mail contains cygcheck results attached.
>Best regards,
>----- Original Message ----- 
>From: "Chris Faylor" <>
>To: "Cygwin" <>
>Sent: 29 ?????? 2000 ?. 19:16
>Subject: Re: Debugging under SMP problem
>> It sounds like you're not running cygwin 1.1.2.  A bug similar to this
>> was fixed there.
>> cgf
>> On Thu, Jun 29, 2000 at 03:00:13PM +0300, Michael V. Nikolaev wrote:
>> >I have latest Cygwin release installed under Windows NT server 4.0 (SP
>> >6a) with dual Pentium II processors (cygcheck output is attached).
>> >When I trying to debug (with latest gdb) any program (just "main(){}")
>> >I get the following exception:
>> >
>> >Program received signal SIGSEGV, Segmentation fault.
>> >0x77f6ce4c in ?? ()
>> >
>> >The executed instruction is "incl 0x10(%eax)" in NTDLL, and eax == 0.
>> >It is executed when cygwin startup code attempts to load advapi.dll.
>> >The previous instruction loads eax with 0 from memory location (mov
>> >(%esi),%eax).  I was trying to debug this program with Borland
>> >Turbodebugger (td32) - the result is the same.  When being debugged on
>> >another, single-processor PC running WinNT WS SP 6a, all is OK, so I
>> >guess that this is Cygwin1.dll problem with SMP-platforms.

Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list