id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
766	psDB errors	David.Robbins@…	jhoblitt	"After paul recently applied Josh's patches to psDB.c, the db tests are ALL
failing.  I get the following output just from the first test, psDBInit:
2006:06:22 20:44:10Z|classdhcp178.mhpcc.hawaii.edu|E|checkMemBlock (psMemory.c:170)
    Memory block 115 was freed but still being used.
2006:06:22 20:44:10Z|classdhcp178.mhpcc.hawaii.edu|A|memProblemCallbackDefault
    Detected a problem in the memory system at psMemGetRefCounter:614
Return value mismatch: expected 0, got -6

After running gdb on this test, I get the following output:
#2  0x00002aaaaaabe904 in psAbort (name=Could not find the frame base for ""psAbort"".
) at psAbort.c:36
#3  0x00002aaaaaac071b in memProblemCallbackDefault (ptr=0x6d5930,
file=0x2aaaaacbd300 ""psMemGetRefCounter"", lineno=614)
    at psMemory.c:145
#4  0x00002aaaaaac143a in psMemGetRefCounter (ptr=0x6d59b0) at psMemory.c:614
#5  0x00002aaaaaadd4c8 in psDBPTypeToSQLTableCleanup () at psDB.c:1712
#6  0x00002aaaaaad8cfa in psDBCleanup (dbh=0x6d5910) at psDB.c:194
#7  0x0000000000405862 in TPDBInit () at tst_psDB.c:533

I know josh just implemented thread safety functions in psDB.  I am of course
willing to work on fixing the issue(s) here, but I thought that perhaps he may
have an idea of what went wrong."	defect	closed	high		db	unspecified	normal	fixed