Re: Write past chunk end? - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Write past chunk end?
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE094639@algol.sollentuna.se
Whole thread Raw
In response to Write past chunk end?  ("Magnus Hagander" <mha@sollentuna.net>)
List pgsql-hackers
> > I'm testing out the latest version of Palles ICU patch on
> win32, and I
> > got the build syste mworking. But it no longer works when
> built - it
> > used to...
> >
> > When initdb:ing with this version and -E UNICODE, I get:
> > WARNING: detected write past chunk end in Analyze Column 01472ED0
>
> Search for a AllocSetContextCreate whose name is "Analyze
> Column"; somebody is writing more memory than allocated.
>
> > Any ideas on how to debug this?
>
> The problem is that it's detected in MemoryContextCheck, long
> after the clobber occured.  You could set a watchpoint in
> gdb, I think.

That's what I was afraid of. Well, some shotgun-debugging later, I found
the problem. A "+1" that should be "+2" because UTF-16 is two-byte... As
the data is freed very soon afterwards this didn't cause a crash, but I
bet it would've given the same warning if it was run on FreeBSD with
debugging and asserts enabled.

Anyway. Thanks, got it sorted.

//Magnus


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Interval->day docs and regression tests
Next
From: "Rocco Altier"
Date:
Subject: Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive times for idle, interval,