[squeak-dev] Fixing the infinite debugger chains? (was: Code simulation error (was Re: I broke the debugger?))
forums.jakob at resfarm.de
Wed Jun 17 23:44:28 UTC 2020
Oh, my 4.5 images open only one debugger for findContextSuchThat:.
That is, one debugger per further click on "Over".
Am Do., 18. Juni 2020 um 01:14 Uhr schrieb Jakob Reschke
<forums.jakob at resfarm.de>:
> Hi all,
> Want another easy way to still get endless debuggers?
> [^ self halt] ensure: [1 asString]
> Do it, then step over the return (I have to click twice actually) -->
> endless debuggers on findContextSuchThat:.
> Triggers in both current Trunk and in 5.3, and 5.2, and 5.0. In 5.1
> and 4.6 I get repeated emergency evaluators instead.
> If you proceed in the debugger after the halt, the expression
> evaluates flawlessly.
> If this example is not actually a new one, just be reminded that the
> problem still exists... ;-)
> Kind regards,
> Am So., 23. Feb. 2020 um 23:45 Uhr schrieb Christoph Thiede
> <christoph.thiede at student.hpi.uni-potsdam.de>:
> > > Unfortunately, for reasons I did not yet figure out, this fixes all
> > recursions listed in my latest post, with exception of Generator>>#nextPut:.
> > Short update: The latter can be explained by looking at Context >>
> > #cannotReturn:, which spawns a debugger on the activeProcess (!) manually.
> > Not sure why we cannot simply raise a regular exception here? This would
> > also be analogous to BlockCannotReturn ...
> > Best,
> > Christoph
> > --
> > Sent from: http://forum.world.st/Squeak-Dev-f45488.html
More information about the Squeak-dev