Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 29 Jun 2000 18:22:57 -0400
To: Cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Debugging under SMP problem
Message-ID: <20000629182257.C8571@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: Cygwin <cygwin AT sourceware DOT cygnus DOT com>
References: <006901bfe1c1$cea26470$6400a8c0 AT olvi DOT org> <20000629121656 DOT G728 AT cygnus DOT com> <003d01bfe217$2e881a60$6400a8c0 AT olvi DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <003d01bfe217$2e881a60$6400a8c0@olvi.org>; from mvn@gu.kiev.ua on Fri, Jun 30, 2000 at 01:12:54AM +0300

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.

cgf

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 sourceware.cygnus.com (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,
>Michael
>----- Original Message ----- 
>From: "Chris Faylor" <cgf AT cygnus DOT com>
>To: "Cygwin" <cygwin AT sourceware DOT cygnus DOT com>
>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 cygwin-unsubscribe AT sourceware DOT cygnus DOT com