Opened 20 years ago
Closed 20 years ago
#766 closed defect (fixed)
psDB errors
| Reported by: | Owned by: | jhoblitt | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | db | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
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.
Change History (3)
comment:1 by , 20 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
comment:2 by , 20 years ago
comment:3 by , 20 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This bug was actually fixed right before changes to psError broke the pre-TAP
test framework. Either way it's no longer relevant.
This is likely my fault. There is going to be some flux with the psDB functions
for the next few days but I'll take care of fixing the tests.