<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 6, 2014 at 7:48 PM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, Oct 4, 2014 at 9:30 AM, Balázs Kósi <<a href="mailto:kosi.balazs@ezomer.hu">kosi.balazs@ezomer.hu</a>> wrote:<br>
> Hi,</span> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
><br>
> Today I came across two nuisances in the debugger:<br>
><br>
> The first one is, that if you try to evaluate code in a debugger started<br>
> from another debugger, you'll get an MNU: MessageAsTempNode>>beMethodArg.<br>
<br>
</span>That's strange, I do that a lot and it works fine for me.<br>
<div class="HOEnZb"><div class="h5"><br>
</div></div></blockquote></div>It's rather easy to reproduce: <br> 1) debug an expression. eg. 3 + 4<br></div><div class="gmail_extra"> 2) from the debugger start another debugger from the code pane or from the pane on the bottom right (with the local variables in scope), but not from the bottom left pane (with the instance in scope as self)<br></div><div class="gmail_extra"> 3) try to evaluate any code in the code pane or in the bottom right pane, and you get a debugger.<br><br></div><div class="gmail_extra">Cheers, Balazs<br></div></div>