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

From Magnus Hagander
Subject Re: Oops - BF:Mastodon just died
Date
Msg-id 20080131084256.GB8942@svr2.hagander.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
Re: Oops - BF:Mastodon just died
List pgsql-hackers
On Thu, Jan 31, 2008 at 12:45:40AM -0500, Tom Lane wrote:
> 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.

Yeah, nice catch. Wouldn't surprise me if we actually had this problem
before, just that the dropped symbols were not actually used by our own
modules. I notice the export count jumped to 5226...


> > 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.

+1

//Magnus


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Oops - BF:Mastodon just died
Next
From: Magnus Hagander
Date:
Subject: Re: 8.3RC1 on windows missing descriptive Event handle names