[Opentnl-general] Server crash just due to TNL_DEBUG??

[boB G. <boB@Gage.net>]

I've found a bizarre situation and I'm hoping it's only happening because 
I'm compiling with TNL_DEBUG turned on.

When I change something in my ghosted data or add an RPC to my server, it 
changes the underlying connection structure enough so that both client and 
server have to be re-built before a sane connection is possible.    This is 
not the problem.

When an old version client connects to my new version server, the client 
crashes.   This also is not the problem.    A short time later (about the 
time my master server notices the connection drop??) my server 
crashes.   THAT is the problem.

Is this just an extreme reaction because I have TNL_DEBUG turned on or 
should I be worried about hackers that get something built on the TNL 
library that's close enough to almost connect, but not quite?

What is the recommended way to implement version control using TNL objects?

Thanks in advance,
boB