Re: Oops - BF:Mastodon just died - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Oops - BF:Mastodon just died
Date
Msg-id 47A13DEB.6060103@dunslane.net
Whole thread Raw
In response to Re: Oops - BF:Mastodon just died  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Oops - BF:Mastodon just died
List 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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Next
From: Tom Lane
Date:
Subject: Re: Oops - BF:Mastodon just died