Debugger and stepping over a function that will have a DNU
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? holger
I think it is known. But there seem to be more problems in the debugger when stepping. So not easy to find the exact culprit Norbert
Am 04.12.2016 um 14:34 schrieb Holger Freyther <holger@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?
holger
2016-12-04 9:04 GMT+01:00 Holger Freyther <holger@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-...>. (last allows interrupt in such cases)
On 5 Dec 2016, at 19:10, Holger Freyther <holger@freyther.de> wrote:
On 05 Dec 2016, at 13:03, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Dear Denis,
It was fixed here 16877 and here 19108. (last allows interrupt in such cases)
is this in Pharo5 or will it show up in Pharo5?
These are good candidates for back porting. I will put it on my TODO. Marcus
On 6 Dec 2016, at 07:10, Marcus Denker <marcus.denker@inria.fr> wrote:
On 5 Dec 2016, at 19:10, Holger Freyther <holger@freyther.de> wrote:
On 05 Dec 2016, at 13:03, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Dear Denis,
It was fixed here 16877 and here 19108. (last allows interrupt in such cases)
is this in Pharo5 or will it show up in Pharo5?
These are good candidates for back porting. I will put it on my TODO.
I added an issue to not forget: https://pharo.fogbugz.com/f/cases/19424/Backport-Debugger-step-fixes-to-Phar... <https://pharo.fogbugz.com/f/cases/19424/Backport-Debugger-step-fixes-to-Phar...> Marcus
participants (4)
-
Denis Kudriashov -
Holger Freyther -
Marcus Denker -
Norbert Hartl