Fix commited in rev 30369.
The related issue is 16664.
Testing this bug is an issue due to its unclear how to provoke it. However the fix is for a programming error and verify of code is good enough test.
It is easily provoked by: 1. Create a session 2. Send SIGSTOP to vsmagent 3. Open the session in tladm Using this I can confirm that the bug is indeed fixed.