Re: [Help-smalltalk] Fix the continue back into GTK/Event-Loop/C-code

[Gwenaël Casaccio]

On 29/10/2013 14:58, Gwenaël Casaccio wrote:
> On 24/10/2013 07:40, Holger Hans Peter Freyther wrote:
> > On Mon, Oct 21, 2013 at 12:55:16PM +0200, Gwenaël Casaccio wrote:
> > > Hi,
> > >
> > > here is a patch that fix the continue back into GTK/Event-Loop/C-code
> > > (with the debugger and text widget).
> > Good Morning,
> >
> > I think I manage to break the TaskQueue
> >
> > Repeat:
> > Open Workspace
> > '1234' do: [:each | each asUpperCase] ALT+D/DebugIt
> > Step until the BlockClosure is executed
> >
> > select "each asUpperCase" CTRL+I => UndefinedObject
> > select "each" CTRL+I => Character
> >
> > in the Inspector type
> > self upperCase CTRL+P Debugger comes up
> > self upperCase CTRL+P nothing
> >
> > Result:
> > Stepping in the debugger is broken, DoIt's don't
> > appear to work either.
> >
> >
> > Proposition:
> > * Name the forked process (so one can identify it)
> > * Keep the process in a local variable so one can
> >    more easily find the process.
> >
> > thanks
> >     holger
>
> Here is a new version with your proposal changes included inside it
> and a new event loop which doesn't use ensure like the last eval patch.
>
> Gwen

I hope it's the last increment :) I've discovered that 
Behavior>>#evaluate: used
valueWithUnwind and that cause an issue with the task queue. I use my onw
eval code which doesn't use valueWithUnwind.

Cheers,
Gwen

0001-Makes-the-debugger-text-widget-non-blocking-and-fix-.patch
Description: Text Data