Ah, okay, yes.  Boom.

On Mon, Oct 6, 2014 at 1:38 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Hi Cris,
>
> On Mon, Oct 6, 2014 at 11:37 AM, Chris Muller <asqueaker at gmail.com> wrote:
>>
>> I just tried those exact instructions in trunk image and it worked.  I
>> tried the expression, 'hello' asUppercase in both the code pane and
>> the lower-right pane, selected "debug" from teh context menu.  It
>> worked for me.
>
>
> you need to go one step further.
>
> 1. debug 3.4.
> 2. in code pane of debugger #1 debug 4+5
> 3. in code pane of debugger #2 debug 5+6, boom.
>
>>
>>
>> On Mon, Oct 6, 2014 at 1:21 PM, Balázs Kósi <kosi.balazs at ezomer.hu> wrote:
>> >
>> >
>> > On Mon, Oct 6, 2014 at 7:48 PM, Chris Muller <asqueaker at gmail.com>
>> > wrote:
>> >>
>> >> On Sat, Oct 4, 2014 at 9:30 AM, Balázs Kósi <kosi.balazs at ezomer.hu>
>> >> wrote:
>> >> > Hi,
>> >>
>> >> >
>> >> > Today I came across two nuisances in the debugger:
>> >> >
>> >> > The first one is, that if you try to evaluate code in a debugger
>> >> > started
>> >> > from another debugger, you'll get an MNU:
>> >> > MessageAsTempNode>>beMethodArg.
>> >>
>> >> That's strange, I do that a lot and it works fine for me.
>> >>
>> > It's rather easy to reproduce:
>> >  1) debug an expression. eg. 3 + 4
>> >  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)
>> >  3) try to evaluate any code in the code pane or in the bottom right
>> > pane,
>> > and you get a debugger.
>> >
>> > Cheers, Balazs
>> >
>> >
>> >
>>
>
>
>
> --
> best,
> Eliot