| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Win32 WEXITSTATUS too simplistic |
| Date: | 2006-12-26 20:01:18 |
| Message-ID: | 28111.1167163278@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"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?"
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-26 21:37:28 | pgsql: Fix failure due to accessing an already-freed tuple descriptor in |
| Previous Message | Andrew Dunstan | 2006-12-26 19:47:41 | Re: Win32 WEXITSTATUS too simplistic |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glen Parker | 2006-12-26 21:59:46 | Re: Patch(es) to expose n_live_tuples and |
| Previous Message | Andrew Dunstan | 2006-12-26 19:47:41 | Re: Win32 WEXITSTATUS too simplistic |