stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farid Zaripov" <Farid_Zari...@epam.com>
Subject RE: negative exit status in Windows builds
Date Wed, 08 Aug 2007 18:53:12 GMT
> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor
> Sent: Wednesday, August 08, 2007 7:20 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: negative exit status in Windows builds
> 
> I've been noticing negative exit status reported in a few 
> test results on Windows. For example, in a 12d build with 
> MSVC 8.0, the following test results are reported:
> 
>    NAME                           STATUS   WARN    REAL
>    21.cwchar.exe             -1073741811      0   0.047
>    22.locale.messages.exe    -1073741811      0   1.282
>    22.locale.time.put.exe    -1073741811      0   0.250
>    27_filebuf.exe            -1073741811      0   0.063

All above: -1073741811 == 0xC000000D == STATUS_INVALID_PARAMETER

//
// MessageId: STATUS_INVALID_PARAMETER
//
// MessageText:
//
//  An invalid parameter was passed to a service or function.
//
#define STATUS_INVALID_PARAMETER         ((NTSTATUS)0xC000000DL)

>    23_allocator.exe          -1073741571      0   0.031

  -1073741571 == 0xC00000FD == STATUS_STACK_OVERFLOW
//
// MessageId: STATUS_STACK_OVERFLOW
//
// MessageText:
//
//  A new guard page for the stack cannot be created.
//
#define STATUS_STACK_OVERFLOW            ((NTSTATUS)0xC00000FDL)    //
winnt

> I suspect it's because exec failing to map the error code(s) 
> to meaningful error strings. Farid, can you reproduce this in 
> your environment? If so, could you quickly see is there's an 
> easy fix? (If not, let me know, I'll open an issue for it in Jira).

  It's easy to fix, but what signals map these values to?

Farid.

Mime
View raw message