Eh... and I still managed to get it wrong, here...

Maybe setting stops gave that behavior, but reviewing
https://github.com/jsoftware/j-playground/issues/31 I see that it was
stopping from an error (as opposed to an explicit stop -- I don't know
if those were ever enabled).

We can still lock up a playground window using that script...

On the plus side, having the popup loop still active means that it
should be possible to debug it.

More specifically, emj.wasm 0x0122fa5 (a call_indirect with a bunch of
parameters which might be zeros) is what triggers the popup. So if we
could figure out what that corresponds to in the C source, that's what
we would have to change to fix this problem.

I'll drop a quick note into that github issue...

FYI,

--
Raul

On Sun, Jul 10, 2022 at 12:01 AM 'robert therriault' via General
<[email protected]> wrote:
>
> In my last report on the J Wiki Meeting of July 7th, I incorrectly stated 
> that Raul through that recursive debugging calls may be problematic. He 
> contacted me with the following information to set the record straight:
>
> Raul: The issue I was thinking about was where it used to be that hitting a 
> stop in a verb in the playground would give a javascript popup. And, 
> attempting to close that javascript popup would bring it back up again. So 
> there was no way to regain control of that browser session -- you had to 
> close the window. More recently, setting stops seems to have been completely 
> disabled in the playground.
>
> Thank you for correcting me Raul, I will update the report that has been put 
> on the wiki accordingly.
>
> Cheers, bob
>
> > On Jul 8, 2022, at 17:32, 'robert therriault' via Programming 
> > <[email protected]> wrote:
> >
> > Raul suggests it would be based on the current 13!: foreigns, but that 
> > recursive debugging calls may be problematic.
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to