From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave Page <dpage(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Oops - BF:Mastodon just died |
Date: | 2008-01-31 03:18:03 |
Message-ID: | 47A13DEB.6060103@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Neither of these sound very plausible, but it seems the next step for
> investigation is to look closely at what's happening in gendef.pl.
>
>
>
Yes, I have found the problem. It is this line, which I am amazed hasn't
bitten us before:
next unless /^\d/;
The first field in the dumpbin output looks like a 3 digit hex number.
The line on my system for GetConfigOptionByName starts with 'A02' which
of course fails the test above.
For now I'm going try to fix it by changing it to:
next unless $pieces[0] =~/^[A-F0-9]{3}$/;
I also propose to have the gendefs.pl script save the dumpbin output so
this sort of problem will be easier to debug.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-31 05:42:07 | Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |
Previous Message | Bruce Momjian | 2008-01-31 02:15:35 | Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |