Front page | perl.perl5.porters |
Postings from March 2007
On 3/13/07, via RT Mark Buxbaum <perlbug-followup@perl.org> wrote: > 0240fbc4 28001971 02965564 00000000 007ffffc perl58!Perl_stashpv_hvname_match+0x8a5 > 0240fbe4 28001e4a 02965564 02966384 007ffffc perl58!Perl_av_store+0x1b8 > 0240fc04 003e241a 00000000 02966384 6d69cf64 perl58!Perl_av_push+0x1fa > 0240fc48 28040019 0e6ecf78 0279d3f8 00000001 shared+0x241a > 0240fc84 2805d49d 012a4394 002a4394 280246cf perl58!Perl_sv_compile_2op+0x7b9f > 0240fd58 280241f5 002a4394 0e6ecf60 00000042 perl58!Perl_runops_standard+0xc > 0240fd6c 280323c6 002a4394 28095504 00000002 perl58!Perl_call_method+0x2b > 0240fd9c 2805d49d 0284e620 002a4394 28023fdf perl58!Perl_Guse_safe_putenv_ptr+0xa248 > 0240fe24 28088a21 002a4394 00000000 00000000 perl58!Perl_runops_standard+0xc > 0240ff3c 00401012 00000003 002a3f28 002a2d38 perl58!RunPerl+0x86 > 0240ffc0 7d4e992a 00000000 00000000 7efdf000 perl+0x1012 > 0240fff0 00000000 00401016 00000000 00000000 kernel32!BaseProcessInitPostImport+0x8d You didn't show your code, you didn't indicate which modules were loaded, you didn't indicate anything about whether you're using any threading features or the Win32 pseudo-fork feature. Providing any of those might help. Contacting ActiveState would also be reasonable since its their build. I'm immediately suspecting some corrupted data because of either bad thread usage or maybe just some buggy XS/C code. Based on where in the code you were probably in av_store, I guess you were writing to some kind of tied variable. I also guess there's muckery afoot in the object backing the tied variable. Its all 100% speculation though. JoshThread Previous