Re: Win32 WEXITSTATUS too simplistic

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Win32 WEXITSTATUS too simplistic
Date: 2006-12-26 22:27:12
Message-ID: 2104.24.211.165.134.1167172032.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> "Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
>> Tom Lane wrote:
>>> Anyone want to run down what we should really
>>> be using instead of the above macros?
>
>> The exit code is apparently what is reported from GetExitCodeProcess().
>> For info on that see
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/getexitcodeprocess.asp
>
>> I think we are possibly seeing the third case, i.e. the code from an
>> unhandled exception. I haven't managed to find an API to handle them
>> though ...
>
> Right ... but I don't think we want to "handle the exception". The
> right question to be asking is "what is the encoding of these 'exception
> values' it's talking about?"
>

Yes, sorry for my loose expression. That's what I meant - I didn't find an
API that would translate the exception values.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-12-26 23:57:10 Re: Rare corruption of pg_class index
Previous Message Joshua D. Drake 2006-12-26 22:26:25 Re: Patch(es) to expose n_live_tuples and

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-12-27 00:02:12 Re: Patch(es) to expose n_live_tuples and
Previous Message Joshua D. Drake 2006-12-26 22:26:25 Re: Patch(es) to expose n_live_tuples and