Re: SEGFAULT in CREATE EXTENSION related pg_init_privs

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SEGFAULT in CREATE EXTENSION related pg_init_privs
Date: 2016-04-14 08:49:52
Message-ID: CAH2-Wz=XSoz16JZt=6Ti+ybX-UiF1aDFTfNQ1adCep=TGDk-Mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 14, 2016 at 1:27 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> (gdb) bt
> #0 heap_deform_tuple (tuple=tuple(at)entry=0x1d87e90,
> tupleDesc=tupleDesc(at)entry=0x7f1dab9525b0, values=values(at)entry=0x1d87a28,
> isnull=isnull(at)entry=0x1d882d8 "\177\177\177\177\177~\177\177") at
> heaptuple.c:881

The memory appears to be freed -- CLOBBER_FREED_MEMORY stuff does this.

You might try using Valgrind, with --track-origins, which will show
where the memory was first allocated.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-04-14 09:13:54 Re: SEGFAULT in CREATE EXTENSION related pg_init_privs
Previous Message Kyotaro HORIGUCHI 2016-04-14 08:48:42 Re: Support for N synchronous standby servers - take 2