Re: [naviserver-devel] Trace errors

[Stephen D. <sd...@gm...>]

On 10/21/05, Vlad Seryakov <vl...@cr...> wrote:
>
> [21/Oct/2005:09:30:55][8454.3004771248][-thread-1290196048-] Error: Can
> not register Tcl trace, server already started.
>
> The trace which is called is NS_TCL_TRACE_DEALLOCATE


This has been the case for quite a while, it just never used to log an
error (which is why the bug in nsdb went unnoticed).

The trace api is limited to pre-start up because the locking would be
a pain.  It's possible for example for a Tcl trace callback to add
another trace, causing a deadlock if we don't use something like a
critical section, which seems a little over the top.

Which code is trying to register a trace, and why?