In a message dated 8/28/02 11:48:47 PM, [EMAIL PROTECTED] writes:
> Subject: ns_param SystemScope obsolete?
>
> Is the ns_param SystemScope obsolete?
>
> Grepping through both the 3.3+ad13 and 4.x (cvs head) sources, I don't
> see it anywhere. It looks to me as if the thread scope is determin
IMO, who cares about being able to crash AS this way? The only scenario
I can see it being important is for a hosting service that lets users
interact directly with TCL. I doubt there are very many of those. And
if it's a big concern there, those sites can easily redefine ns_rwlock
to add array
In a message dated 8/29/02 11:48:19 PM, [EMAIL PROTECTED] writes:
> Date: Thu, 29 Aug 2002 15:46:57 +0100
> From: Harry Moreau <[EMAIL PROTECTED]>
> Subject: How to crash AOLserver 3.4 in one line of tcl...
>
> The line is
>
> ns_rwlock destroy rid0x83daf50
>
> providing that rid0x83daf