| delorie.com/archives/browse.cgi | search |
On Jul 16 04:21, Reini Urban wrote: > 2009/7/16 Reini Urban: > > 2009/7/15 Steven Hartland: > >> 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. > >> > >> According to gdb 0x610d089d = thread.cc:113 > > > > Thanks! > > > > This looks like almost certainly a simple perl bug. Threads was Jerry Heddens > > working arena lately, but there are complicated things going in core. > > If it's easily reproducible best would be to start with a debugging perl > > and break at the point which tries to read from 0x4. > > Sorry, cannot reproduce either > with the following perls: 5.8.5 5.8.5d 5.8.6 5.8.8 5.10.0 5.10.0d 5.11.0d > under cygwin-1.5.25 and XP SP2 > and neither under latest cygwin-1.7.0 It's a Windows Server 2008 thingy. MSFT added some code to the OS which checks for the validity of the SEH chain. The code is not compiled in to the client OSes, only to the Server OSes. We checked in a patch back in early 2008 to deal with this mechanism. That's probably the reason that the C testcase works fine. Apparently Perl adds something which makes the SEH chain invalid again from 2008's point of view. Btw., *everybody* can test on Windows Server 2008: http://www.microsoft.com/downloads/details.aspx?familyid=B6E99D4C-A40E-4FD2-A0F7-32212B520F50 Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |