Well beyond the simple memory access violation (seg fault) type of failure then. (a) if you have configured your vm to use a limited amount of memory and you enter a recursive loop the VM likely will thrash thru the available memory in a small number of milliseconds on a fast machine then exit(). I believe by default it's 1GB, but if there is no paging involved to find 1GB of ram it can happen quite quickly. (b) Older unix/linux vm are susceptible to crashing if they expand image memory over the 2GB address boundary. I can't say exactly what version that would be, but if you supply the build information for your VM SmalltalkImage current getSystemAttribute: 1004 and SmalltalkImage current getSystemAttribute: 1006 That might give a clue to if the fixes for the problem are in the VM you are using. On 2009-11-03, at 11:08 AM, Schwab,Wilhelm K wrote:
John,
I would be happy to give a reproducible example, but one eludes me at present. To add to the fun, I have now seen the image quit on a second Linux box; this time, my laptop. I am fairly certain that it crashed over a mouse wheel event.
Both machines are running Ubuntu 9.10, which might be the trigger of my new-found hassles.
Bill
-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================