Re: [HACKERS] Win32 WEXITSTATUS too

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Chuck McDevitt <cmcdevitt(at)greenplum(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Takayuki Tsunakawa <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Subject: Re: [HACKERS] Win32 WEXITSTATUS too
Date: 2007-01-23 18:17:23
Message-ID: 45B65133.6080301@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Chuck McDevitt wrote:
> Win32 exception codes start with a two-bit severity indication.
> 00 means "success", so nothing is wrong.
> 01 is an "informational" messages.
> 10 is a "warning" message.
> 11 is an "error".
>
> That's why the common exception codes you see start with hex C0, as they
> are "errors".
>
> The rest of the top 16 bits are the "facility" that caused the error.
> Often not filled in.
>

Almost, AAUI. The next significant bit after the severity bits is a
custom flag - 0 indicates it is a MS exception, 1 that it's from a third
party. The remaining upper 13 bits are the facility.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-01-23 18:30:57 Re: "tupdesc reference is not owned by resource owner Portal" issue in 8.2 and -HEAD
Previous Message Chuck McDevitt 2007-01-23 17:55:33 Re: [HACKERS] Win32 WEXITSTATUS too

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2007-01-23 23:26:39 Re: server process (PID xxx) was terminated by signal
Previous Message Chuck McDevitt 2007-01-23 17:55:33 Re: [HACKERS] Win32 WEXITSTATUS too