[Vm-dev] [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

Eliot Miranda eliot.miranda at gmail.com
Fri Aug 24 17:39:42 UTC 2018

Hi Sean,
On Fri, Aug 24, 2018 at 10:03 AM Sean P. DeNigris <sean at clipperadams.com>

> Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the
> following:
> <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg>
> This seems to usually signal that a crash is not far away. It's doubly
> concerning because there is no clear way to stop the troubled process
> (interrupts often bring up a debugger on something else) and because, since
> one is now unable to save any code, it's unclear how to start over easily
> in
> a new image. In an extreme scenario, I recently panicked during such an
> experience and accidentally clicked "Save" instead of "Save As…" resulting
> in an image that took hours worth of code (I know maybe not a great
> practice) with it to the grave.
> Any idea why this happens or what we might be able to do anything about it?

No. Yes. Indirectly I hope to help debug this.  I am nearly finished with
an error handling facility in the VM for FFI calls that will fail an FFI
callout primitive with an error code indicating the kind of exception and
the pc.  This should at least stop the system from crashing and give us an
improved ability to make sense of the exception; at least we'll be able to
examine the arguments to the call.  More details as I roll out the
facility.  It will require integrating some support code, rewriting FFI
callout signatures to include an error code, etc.

p.s. I was so concerned that I immediately resolved to move to Pharo 7, but
> that turned out not to be an option do to the recently reported bug with
> extension methods (that don't exactly match the package name)
> -----
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180824/9bb922b4/attachment.html>

More information about the Vm-dev mailing list