On Tue, Feb 08, 2011 at 06:31:23PM +0100, strk wrote:
> I see pg_parser_errhint is calling lwmessage_truncate and passing
> it (lwg_parser_result->errlocation-1) w/out first checking
> errlocation begin <= 0 (checked shortly after).
I've committed a fix for the problem of my guess in r6789.
--s
On Tue, Feb 08, 2011 at 08:54:12AM +0100, Peter Hopfgartner wrote:
> >> Program terminated with signal 11, Segmentation fault.
> >> #0 0x0035eee79c00 in strncat () from /lib64/libc.so.6
> >> (gdb) bt
> >> #0 0x0035eee79c00 in strncat () from /lib64/libc.so.6
> >> #1 0x2b9176d04282 i
Hi Mark!
>On 04/02/11 07:20, Peter Hopfgartner wrote:
>
>> We do have code dumps enabled on our developement servers and, from
>time to time, some PostgreSQL/PostGIS process dumps core.
>> Could some useful feedback be provided to the developers from these
>dumps? Is the back trace enough, like th
On 04/02/11 07:20, Peter Hopfgartner wrote:
We do have code dumps enabled on our developement servers and, from time to
time, some PostgreSQL/PostGIS process dumps core.
Could some useful feedback be provided to the developers from these dumps? Is
the back trace enough, like the following:
Pr
We do have code dumps enabled on our developement servers and, from time to
time, some PostgreSQL/PostGIS process dumps core.
Could some useful feedback be provided to the developers from these dumps? Is
the back trace enough, like the following:
Program terminated with signal 11, Segmentation f
