Re: server: Avoid accessing free'd thread pointers.

[Alexandre Julliard]

Eric Pouech  writes:
> I've seen it too, but it was only for current cursor not next, which 
> still means we have :
> - the issue in process termination, where an iteration in the loop can
>
> kill more than one item in the list

This is fixed now.
> - the generic issue in the SAFE version, where we still access the
>
> cursor after it has been potentially fixed

No, in the SAFE macros we don't, that's the whole point of having
them.