Re: Segmentation fault with core dump

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Joshua Berry <yoberi(at)gmail(dot)com>
Cc: PostgreSQL - General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Segmentation fault with core dump
Date: 2013-04-10 23:28:57
Message-ID: 20130410232857.GA10264@awork2.anarazel.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2013-04-10 18:25:24 -0500, Joshua Berry wrote:
> > Ok, I might be seeing whats going on here. Could you go to 'printtup'
> > and print *myState, *myState->attrinfo, *typpeinfo?
> >
>
> #4 0x00000000004593c4 in printtup (slot=0x2d14618, self=0x2a50c40)
> at printtup.c:297
> 297 printtup_prepare_info(myState, typeinfo, natts);
> (gdb) print *myState, *myState->attrinfo, *typeinfo
> value has been optimized out

Hm. Make that a
print *(DR_printtup *) self
print *((DR_printtup *) self)->attrinfo
print *slot->tts_tupleDescriptor

then.

Thanks,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2013-04-10 23:29:06 Re: Segmentation fault with core dump
Previous Message Joshua Berry 2013-04-10 23:25:24 Re: Segmentation fault with core dump