On Thu, Nov 01, 2018 at 12:27:23PM -0300, Alvaro Herrera wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > heap_attisnull (tup=0x0, attnum=5, tupleDesc=0xb2990ef4) at ./build/../src/backend/access/common/heaptuple.c:403
> > 403 ./build/../src/backend/access/common/heaptuple.c: Datei oder Verzeichnis nicht gefunden.
> > (gdb) thread apply all bt full
> >
> > Thread 1 (Thread 0xb4c429c0 (LWP 22367)):
> > #0 heap_attisnull (tup=0x0, attnum=5, tupleDesc=0xb2990ef4) at
./build/../src/backend/access/common/heaptuple.c:403
> > __func__ = "heap_attisnull"
> > #1 0x0087690d in ri_NullCheck (tupDesc=0xb2990ef4, tup=0x0, riinfo=0x2e1d548, rel_is_pk=true) at
./build/../src/backend/utils/adt/ri_triggers.c:2894
> > attnums = 0x2e1d5a4
> > i = 0
> > allnull = true
> > nonenull = true
> > #2 0x00879bf7 in RI_FKey_cascade_del (fcinfo=0xbfbda9e4) at ./build/../src/backend/utils/adt/ri_triggers.c:917
>
> Can you 'print trigdata' in frame 2?
Does this help at all ?
(gdb) frame 2
#2 0x00879bf7 in RI_FKey_cascade_del (fcinfo=0xbfbda9e4) at ./build/../src/backend/utils/adt/ri_triggers.c:917
917 ./build/../src/backend/utils/adt/ri_triggers.c: Datei oder Verzeichnis nicht gefunden.
(gdb) print trigdata
$1 = (TriggerData *) 0xbfbdaca4
It is from another run, however.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
