did you tried in different methods? Stef
On Feb 20, 2009, at 7:45 PM, Schwab,Wilhelm K wrote: > Stef, > > So far, it might be just you??? I tried the following in 10236 and > can proceed from the first halt (either on the notifier or in the > full debugger) and see the second. > > Have I matched your scenario? I've even tried going elsewhere in > the callstack and been ok. In fact, I would prefer the debugger to > pick an earlier frame in most (all?) situations; e.g. it selects the > #halt method rather than the sender, which is what Dolphin has lead > me to expect. > > Bill > > > > DoubleHale>>tryMe > > 2 + 3. > self halt. > 4+5. > self halt. > > " > DoubleHalt new tryMe. > " > > -----Original Message----- > From: [email protected] > [mailto:[email protected] > ] On Behalf Of Stéphane Ducasse > Sent: Friday, February 20, 2009 1:29 PM > To: Pharo Development > Subject: [Pharo-project] Problem with the OB debugger > > Hi > > today I was giving lectures with the pahro-dev image and its OB- > debugger ad I noticed that > I could not have two halts else after proceeding the first one I got a > resume I do not what > and I could not see the other halt. > Is it only me? > > Stef > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
