Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 29 Jun 2000 18:48:55 -0400 To: Cygwin Subject: Re: Debugging under SMP problem Message-ID: <20000629184855.A8833@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: Cygwin References: <00ec01bfe21a$e1717740$67241004 AT homepc DOT freedsl DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <00ec01bfe21a$e1717740$67241004@homepc.freedsl.com>; from avr_fan@nettaxi.com on Thu, Jun 29, 2000 at 03:38:44PM -0700 The project web page is: http://sourceware.cygnus.com/cygwin/ Look for the CVS link. cgf On Thu, Jun 29, 2000 at 03:38:44PM -0700, Dave Arnold wrote: >hi, > >Is there a simple guide to start using CVS to check out the latest >fixes/changes to cygwin stuff? I've never used CVS before. > >Can I access it from bash.exe with simple commands? >A link to a good online tutorial or docs would be useful. > >/dAVe > >-----Original Message----- >From: Michael V. Nikolaev >To: Cygwin >Date: Thursday, June 29, 2000 3:14 PM >Subject: Re: Debugging under SMP problem > > >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" >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 cygwin-unsubscribe AT sourceware DOT cygnus DOT com