-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in Strawberry Perl 64 5.16 #12622
Comments
From tbauer@tibco.comI have a PERL application server using Sockets. The application works on UNIX PERL, and also works on Windows when using Strawberry 5.10. However when it runs on Strawberry 5.16, PERL crashes and I receive a Windows exception report (attached). I have tried the 32 bit and 64 bit versions and receive the same error. Any idea what is happening? Thanks |
From @LeontOn Wed, Nov 28, 2012 at 12:04 AM, Tom Bauer <perlbug-followup@perl.org> wrote:
The report doesn't say much. Can you send a script that shows this Leon P.S. The text of your email shows up weirdly, both in gmail and the |
The RT System itself - Status changed from 'new' to 'open' |
From @nwc10On Fri, Nov 30, 2012 at 02:44:44PM +0000, Tom Bauer wrote:
I doubt that anyone active on the mailing list that deals with bug reports Leon asked for a stack trace. Are you able to generate a textual stack trace?
A small script that reproduces the issue is most useful. The more platform Nicholas Clark |
From @janduboisOn Tue, Dec 11, 2012 at 7:02 AM, Nicholas Clark <nick@ccl4.org> wrote:
A mini-dump is a severy stripped down core file for Windows. It is
I think I can see the crashing instruction: perl516+1090d6 I strongly suspect that this is the "free to wrong pool" error in win32/vmem.h: int *nowhere = NULL; I can see the list of loaded modules, but don't see any threading
I would also try to use the win32-vanilla@perl.org mailing list; the Cheers, |
From @bulk88Since Tom Bauer's 2nd post never made it onto RT for some reason I will Tom Bauer wrote:
-- |
From @bulk88 |
From @bulk88On Tue Dec 11 10:03:52 2012, jdb wrote:
Correct. In 32 bit strawberry perl 5.16.1 (I dont have a 5.16.2 that is used by Poor to no C debugging ability, is one of the reasons to not use To the OP, this might be a Perl the interpreter problem or an XS -- |
From @robschaberFirst time using this bug tracker, forgive me if I've sent this to the use threads; On my machine (Windows 7 x64, version 6.1.7601), this crashes within a ActivePerl 5.16.1.1601 (x64 and x86) ...and runs indefinitely on: Strawberry 5.12.3.0 (x64) Decreasing the number of threads or increasing the length of the timeout I tried to follow bulk88's suggestions in this thread regarding ==================================================================== EXCEPTION: First-chance exception at 0x774512f7 in perl.exe: 0xC0000008: An invalid ==================================================================== CALL STACK:
==================================================================== DISASSEMBLY: 0000000077451001 add dword ptr [rax+66000000h],896F0F44h ==================================================================== C:\Perl>perl -V Platform: Characteristics of this binary (from libperl): ==================================================================== Hopefully some of that is relevant. I don't really know my way around a Thanks. |
From @mnz2000Hello! I found this bug report because my Perl script keeps crashing I can confirm that rschaber's test script crashes on my machine with Building perl 5.18.0 from source with Microsoft Visual Studio 2005 (full To fix: Comment out line 476 in win32/win32sck.c (ActiveState 5.16.3 err = closesocket(osf); This fixes rschaber's test script on both 5.16.3 and 5.18.0. I haven't I have no idea if this is the right way to fix this, and if the To me, the biggest mystery regarding this bug is why Windows is Related report: Perl crash when run under AppVerifier Thanks to rschaber for creating a simple test script! It would have - Mikko |
From @LeontOn Thu, Aug 8, 2013 at 7:00 PM, Mikko Noromaa via RT
Given the use of threads that actually makes sense. There is a race Leon |
From @bulk88On Thu Aug 08 10:00:33 2013, mnoromaa wrote:
I was able to reproduce it effortlessly with a 32 bit perl on Server
Yes, this is a big mystery. CloseHandle returns a bool with GLR error In one process run that I was NOT able to ever reproduce again in the I haven't run this on Win XP. And some tools I would use to further
Attaching pics from my debugging session. -- |
Migrated from rt.perl.org#115934 (status was 'open')
Searchable as RT115934$
The text was updated successfully, but these errors were encountered: