Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 29 Jun 2000 12:16:56 -0400 To: Cygwin Subject: Re: Debugging under SMP problem Message-ID: <20000629121656.G728@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Cygwin References: <006901bfe1c1$cea26470$6400a8c0@olvi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <006901bfe1c1$cea26470$6400a8c0@olvi.org>; from mvn@gu.kiev.ua on Thu, Jun 29, 2000 at 03:00:13PM +0300 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@sourceware.cygnus.com