2016-12-04 9:04 GMT+01:00 Holger Freyther <hol...@freyther.de>: > Hi, > > before I try to reproduce this exactly I wondered if the following is a > known issue with Pharo5. If I am in the debugger and try to step over a > message send and that would generate a DNU, Pharo starts taking 99% cpu > time. If I use CMD+./CTRL+. to interrupt it doesn't really work either. I > get it to repaint the screen once and see a lot of message boxes with > errors but the system remains unresponsive. > > Is that known? >
It was fixed here 16877 <https://pharo.fogbugz.com/f/cases/16877/another-endless-debugger-loop> and here 19108 <https://pharo.fogbugz.com/f/cases/19108/Logging-error-stack-should-not-hang-image-and-prevent-opening-debugger>. (last allows interrupt in such cases)
