On Tuesday 05 November 2002 18:06, you wrote: > > Another try... > > Do you use "clock format ... -gmt 1" somewhere in your Tcl code? > > clock format, but not with -gmt 1. >
Hm, first line of defence did not hold :( So, somebody is freeing (or reallocating) already freed memory or just passing bogus address to the allocator. This *could* be tricky... I have extensively checked the new allocator with Purify since it was introduced in 8.4.0. It works fine. We did not have any memory-related problems reported since 8.4.0 AFAIK, but this should't be of much importance because majority of Tcl users run w/o threads. Hm... Do you have any home-brewn C-level extensions loaded? Or, better yet, what extensions do you have loaded? The problem is *probably* somewhere in thread-exit. You say, you kick a thread or two with ns_schedule_proc? There might be something bad happening during teardown. It would be interesting to know wether the same (core) happens when/if you (can) schedule a proc w/o extra thread (i.e. w/o -thread option)? Zoran
