11 Feb
2009
11 Feb
'09
2:48 a.m.
Folks -
I've seen references to that particular error in the Unix VM in other discussions. We have this problem right now in a slightly different context (an external library call reports that error) and I am wondering if someone can explain to me what causes this error and whether there is a way to "fix" the Unix VM not to cause it.
Thanks for any insights!
Cheers, - Andreas