A simple example, and a mantis/pharo bug report/ would be helpful. In looking at the code the printOn: for example invokes primitiveSocketConnectionStatus and that C code seems fairly paranoid about it's use of a private pointer that points to the supposed operating system data. However without an example it's hard to finger what is at fault.
Also you could run the VM under gnu debug then at the crash you can invoke in the Gnu debugger cmd line call (int) printAllStacks() That will at least indicate the squeak Process stacks to give a clearer example of how the crash occurs. On 2009-11-02, at 7:22 PM, Schwab,Wilhelm K wrote: > John, > > By crash, I mean pretty much the standard thing: one instant, Pharo > is running, click something on the inspector, and suddenly Pharo is > gone. Not good. > > Bill > > -- = = = ======================================================================== John M. McIntosh <[email protected]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
