|
Boost Testing : |
Subject: Re: [Boost-testing] bjam.exe crashed (differently?), took other apps down with it
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2014-04-02 23:11:11
AMDG
On 04/02/2014 07:35 PM, Jim Bell wrote:
> Note that my F: drive is NOT a network share. Could there be some other
> volume flag(s) to check on the drive?
>
> Another bjam.exe crash, again running the regression for MinGW-w64-4.7,
> and took other apps down as before.
>
> This time, it was --tag=master, and the Windows Event Log looks different:
>
> Faulting application name: bjam.exe, version: 0.0.0.0, time stamp:
> 0x5335e604
> Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time
> stamp: 0x51fb1116
> Exception code: 0xc00000fd
>
In ntstatus.h:
//
// MessageId: STATUS_STACK_OVERFLOW
//
// MessageText:
//
// A new guard page for the stack cannot be created.
//
#define STATUS_STACK_OVERFLOW ((NTSTATUS)0xC00000FDL) // winnt
I need a (symbolic) stack trace for the crash to
debug it. It may take a bit of work to get a
release+debug symbols build of bjam, though.
It seems to be supported for gcc only.
In Christ,
Steven Watanabe