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

From Tom Lane
Subject Re: Oops - BF:Mastodon just died
Date
Msg-id 472.1201758340@sss.pgh.pa.us
Whole thread Raw
In response to Re: Oops - BF:Mastodon just died  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Oops - BF:Mastodon just died  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> 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. 

Argh, so it was crossing a power-of-2 boundary that got us.  Good catch.

> For now I'm going try to fix it by changing it to:
>         next unless $pieces[0] =~/^[A-F0-9]{3}$/;

Check.

> I also propose to have the gendefs.pl script save the dumpbin output so 
> this sort of problem will be easier to debug.

Agreed, but I suggest waiting till 8.4 is branched unless you are really
sure about this addition.  We freeze for 8.3.0 in less than 24 hours.
        regards, tom lane


pgsql-hackers by date:

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