Re: [Squeak-VMdev] InterpreterSimulator fixes v2 (works!)

[Ned K. <ne...@sq...>]

On Saturday 03 April 2004 11:19 pm, Tim Rowledge wrote:
> In message <200...@sq...>
>
>           Ned Konz <ne...@sq...> wrote:
> > > Ned, if you put a 'self halt'in BitBltSimulation>initialiseModule does
> > > it actually open a debugger for you? All I get is ... stop.
> >
> > I get the same thing. However, I can actually run Morphic, so *most* of
> > the simulator seems to be working.
>
> Well that's a relief - if I were getting different behaviour at that
> level I'd be really pissed off.
>
> Certainly there's some very odd stuff happening with errors.
>
> Good news I can actually get a MVC image up in sim. Who knows
> what tomorrow will bring?

Fun fact: we get a debugger if we use #profileSends: instead of just 
#runForNBytes:

Another fun fact: when you hit the halt the UIProcess gets killed off and 
restarted (this is of course why your loop stops). Try this:

* put your halt in initialiseModule as before
* open a ProcessBrowser, note the ID of the UI process
* do this in a workspace:

	p := Processor activeProcess.
	sim test. "stops without a clue"

* update the ProcessBrowser

You will see the old activeProcess suspended in the list.

Note that you can't debug it.

Apparently the fork of the new UI process happens, but the debugger is not 
opening in it.

Hmmm... try running the simulator from an MVC project. You get the debugger.

Maybe something is referring to the uiProcess, ScheduledController, or some 
other global state and so is fooling the debugger into not opening correctly.

-- 
Ned Konz
http://bike-nomad.com/squeak/