> On 6 Dec 2016, at 07:10, Marcus Denker wrote:
>
>
>> On 5 Dec 2016, at 19:10, Holger Freyther wrote:
>>
>>
>>> On 05 Dec 2016, at 13:03, Denis Kudriashov wrote:
>>>
>>>
>>
>> Dear Denis,
>>
>>
>>> It was fixed here 16877 and here 19108. (last allows interrupt in such
>>> cases)
>>
2016-12-05 23:10 GMT+01:00 Holger Freyther :
> > 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?
It was fixed only in Pharo 6. it should be mentioned in issue parameters
> On 5 Dec 2016, at 19:10, Holger Freyther wrote:
>
>
>> On 05 Dec 2016, at 13:03, Denis Kudriashov 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 can
> On 05 Dec 2016, at 13:03, Denis Kudriashov 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?
thank you
holger
2016-12-04 9:04 GMT+01:00 Holger Freyther :
> 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+./C
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 :
>
> Hi,
>
> before I try to reproduce this exactly I wondered if the following is a known
> issue with Pharo5
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 g
