X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-499003.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org X-MDAV-Processed: mail1.multiplay.co.uk, Wed, 15 Jul 2009 01:41:25 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 15 Jul 2009 01:41:23 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 188.220.16.97 X-Return-Path: prvs=144737c3d0=killing AT multiplay DOT co DOT uk X-Envelope-From: killing AT multiplay DOT co DOT uk X-MDaemon-Deliver-To: cygwin AT cygwin DOT com Message-ID: <6D01817BC10A4430AFE7A590CC935C09@multiplay.co.uk> From: "Steven Hartland" To: References: <4A5CCB8E DOT 3050105 AT gmail DOT com> <894CDBC00A124EF386FE3A334A73DFB8 AT multiplay DOT co DOT uk> <20090714185506 DOT GB12236 AT ednor DOT casa DOT cgf DOT cx> <20090714190436 DOT GO27613 AT calimero DOT vinschen DOT de> <20090714200631 DOT GP27613 AT calimero DOT vinschen DOT de> <20090714205617 DOT GA12534 AT ednor DOT casa DOT cgf DOT cx> <8541BCA91FF64580AA7A8065FBF9C938 AT multiplay DOT co DOT uk> <39B3B148DA514671BB2E1AE46946169C AT multiplay DOT co DOT uk> <20090715000331 DOT GA5635 AT ednor DOT casa DOT cgf DOT cx> Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on 1.5.25 = instant crash ) Date: Wed, 15 Jul 2009 01:41:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com ----- Original Message ----- From: "Christopher Faylor" To: Sent: Wednesday, July 15, 2009 1:03 AM Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on 1.5.25 = instant crash ) > On Wed, Jul 15, 2009 at 12:36:56AM +0100, Steven Hartland wrote: >>This may or may not help: >> >>According to VC++ debugger it always dies with: >>Unhandled exception at 0x610d089d in perl.exe: 0xC0000005: Access violation reading location 0x00000004. > > No, sorry, it really doesn't help. The VC++ debugger doesn't know how > to handle cygwin exceptions. Was just trying to get a hint of the area of the problem since gdb doesn't actually break when it happens this seemed to be the only way to get that info. Any pointers on how I can help narrow down the issue? Regards Steve -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple