Send me 'x' file and I'll try to help you.
Itai Zukerman wrote:
(gdb) p (*newtup)[0]
$147 = {t_tid = {ip_blkid = {bi_hi = 0, bi_lo = 34}, ip_posid = 1}, t_info = 136}
(gdb) p (*newtup)[1]
$148 = {t_tid = {ip_blkid = {bi_hi = 65510, bi_lo = 65535}, ip_posid = 65535}, t_info
= 24575}
(gdb) p
Just before the return from gistSplit() I see this:
(gdb) p (*newtup)[0]
$147 = {t_tid = {ip_blkid = {bi_hi = 0, bi_lo = 34}, ip_posid = 1}, t_info = 136}
(gdb) p (*newtup)[1]
$148 = {t_tid = {ip_blkid = {bi_hi = 65510, bi_lo = 65535}, ip_posid = 65535},
t_info = 24575}
(gdb) p nlen
(gdb) p (*newtup)[0]
$147 = {t_tid = {ip_blkid = {bi_hi = 0, bi_lo = 34}, ip_posid = 1}, t_info = 136}
(gdb) p (*newtup)[1]
$148 = {t_tid = {ip_blkid = {bi_hi = 65510, bi_lo = 65535}, ip_posid = 65535},
t_info = 24575}
(gdb) p nlen
$149 = 2
(*newtup)[1] doesn't look right,
Itai Zukerman [EMAIL PROTECTED] writes:
I'm still not having any luck tracking down my SEGV. If anyone is
interested in debugging or even just reproducing this, I'd be happy to
post or E-mail you my code. It looks like shortly after calling
gistSplit() there's maybe a double-free()
I'm still not having any luck tracking down my SEGV. If anyone is
interested in debugging or even just reproducing this, I'd be happy to
post or E-mail you my code. It looks like shortly after calling
gistSplit() there's maybe a double-free() somewhere?
It might help to build with
Itai Zukerman [EMAIL PROTECTED] writes:
After recompiling with --enable-cassert, nserting into an empty table,
I get:
TRAP: FailedAssertion(!((VfdCache[0].fd == (-1))), File: fd.c, Line: 1113)
Begins to look like a plain old wild store: ain't *nothing* should ever
write into VfdCache[0].fd.
Tom Lane wrote:
Itai Zukerman [EMAIL PROTECTED] writes:
After recompiling with --enable-cassert, nserting into an empty table,
I get:
TRAP: FailedAssertion(!((VfdCache[0].fd == (-1))), File: fd.c, Line: 1113)
Begins to look like a plain old wild store: ain't *nothing* should ever
TRAP: FailedAssertion(!((VfdCache[0].fd == (-1))), File: fd.c, Line: 1113)
If this is a system that supports hardware watchpoints (like Linux on
x86), then you should be able to do a watch VfdCache[0].fd.
That's exactly what I did, and tracked the problem down to a typo in
my code *blush*.
