so strcmp is being called a lot but klook isn't. that means that klook is looping inside, which basically means the p->next pointer is pointing at itself.
final script: kw mem(kw, "30X") // dumps hash table *(kw+25*4) mem(*(kw+25*4), "16X") // dumps entry for 'in' *(**(kw+25*4)\s) // should print 'in' i expect that the value printed for *(kw+25*4) in the third line will also be the third value printed by the mem on the fourth line, meaning that the hash table entry in question has a next pointer pointing at itself. assuming that is true, i think we're close to the end of what can be done. the hash table list isn't supposed to loop back on itself but it is. that means some kind of dangling pointer or other memory corruption error, which we're not likely to find retroactively. russ
