Front page | perl.perl5.porters |
Postings from December 2012
On Tue, Dec 11, 2012 at 7:02 AM, Nicholas Clark <nick@ccl4.org> wrote:
> On Fri, Nov 30, 2012 at 02:44:44PM +0000, Tom Bauer wrote:
>> Hi Leon
>>
>> I am re-sending this in text mode in case HTML mode was causing problems.
>> Attached is a zip file that contains the mini-dump. Hopefully this will have the information that you need to look at this. Unfortunately the application that is crashing is a server side application. I cannot find a way to narrow down the cause of the failure.
>
> I doubt that anyone active on the mailing list that deals with bug reports
> can process whatever a "mini-dump" is. I don't even recognise the format,
> let alone have any tools to deal with one. (I'm not using Windows)
A mini-dump is a severy stripped down core file for Windows. It is
really only useful for device driver bugs as it doesn't contain the
user-mode call stack.
> Leon asked for a stack trace. Are you able to generate a textual stack trace?
I think I can see the crashing instruction:
perl516+1090d6
713c90d6 c7050000000000000000 mov dword ptr ds:[0],0
I strongly suspect that this is the "free to wrong pool" error in win32/vmem.h:
int *nowhere = NULL;
Perl_warn(aTHX_ "Free to wrong pool %p not %p",this,ptr->owner);
*nowhere = 0; /* this segfault is deliberate,
I can see the list of loaded modules, but don't see any threading
related (or incompatible) XS modules that may be obvious suspects, so
I have no idea why that may have triggered.
>> If this does not help, I can probably find a way to ship you the application that can reproduce the issue.
I would also try to use the win32-vanilla@perl.org mailing list; the
people who build StrawberryPerl hang out there and may be able to
suggest additional debugging options.
Cheers,
-Jan
Thread Previous
|
Thread Next