Peter,
Have you read the info on the Wiki about the CPU monitor etc.? The only remotely long-duration sessions I've done with Squeak have been (3.2 gamma, I think) on Win2k for a couple of days at a time, and it's done well.
I have an intermittent (but persistent) problem with a lockup on Win95 in a MIDI app; that can take seconds or hours to show up, but, the VM seems to keep running, the Morphic UI freezes. I'm slowly shifting hardware around in hopes of trying the same thing on another computer and OS without "destroying" the machine with the reproduceable problem.
The short version is that I'm very interested in seeing how one debugs such things in Squeak. To date, I've gotten crash dumps from it by enabling 3D hardware acceleration on a particular machine; the results leave me confident that if something similar happened in my code, I'd at least know where to start looking for the problem. So far though, I've not been able to wear down the lockup.
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bills@anest4.anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029
Bill,
I have an intermittent (but persistent) problem with a lockup on Win95 in a MIDI app; that can take seconds or hours to show up, but, the VM seems to keep running, the Morphic UI freezes. I'm slowly shifting hardware around in hopes of trying the same thing on another computer and OS without "destroying" the machine with the reproduceable problem.
The short version is that I'm very interested in seeing how one debugs such things in Squeak.
It is very hard to do this. Partly because you need low-level VM tools to look into some of these issues. In particular if they only happen on some machines it means that some assertion of the VM about its hosting platform is wrong. And that means you need to go into it very low-level. There are some features that might help (I added for instance the ability to list all socket state in order to find some of the socket related problems) but this doesn't replace a debugger. Since all of the VM maintainers test quite heavily across all (available) flavours of OSes it also means that the code "ought to work" as it is.
To date, I've gotten crash dumps
from it by enabling 3D hardware acceleration on a particular
machine;
That machine wouldn't use a graphics card which is based on a RIVA TNT chip on Win98, would it?! I just got a totally weird crash report from such a configuration but since I don't have access to it it's almost impossible to do remote debugging.
Cheers, - Andreas
That machine wouldn't use a graphics card which is based on a RIVA TNT chip on Win98, would it?! I just got a totally weird crash report from such a configuration but since I don't have access to it it's almost impossible to do remote debugging.
I have an nVidia TNT3 and Win98. Never had any problems with the D3D VM. Any steps to reproduce?
-Eric
squeak-dev@lists.squeakfoundation.org
-
Andreas Raab -
Bill Schwab -
Eric Scharff