On 9/6/2010 9:59 PM, Florin Mateoc wrote:
>   On 9/7/2010 12:48 AM, Andreas Raab wrote:
>> On 9/6/2010 9:34 PM, Florin Mateoc wrote:
>>>    On 9/6/2010 9:56 PM, Andreas Raab wrote:
>>>> That leads me to believe that we're getting all the way through Debugger class openOn:context:label:contents:fullView:
>>>> to the end where it says "process suspend" and no new MVC process is being spawned.
>>>>
>>>> And that's about where my MVC knowledge ends these days. Any ideas how to spawn the proper MVC scheduler process? It's
>>>> probably some equvilant to #spawnNewProcessIfThisIsUI: in Morphic but I don't know the magic incantation.
>>>>
>>> It should be ScheduledControllers searchForActiveController, but I suspect ScheduledControllers is nil (it should be an
>>> instance of ControlManager)
>>
>> This doesn't sound right to me. ScheduledControllers isn't nil (it's "a ControlManager") since I'm running this code
>> from MVC, but #searchForActiveController ends with "Processor terminateActive" which seems decidedly wrong for a
>> situation where we want to *debug* the process, not terminate it.
>>
>> However, if I instead use ScheduledControllers>>spawnNewProcess (which looks vaguely correct in such that it's indeed
>> the equivalent of #spawnNewProcessIfThisIsUI:) the result is no lockup, but no debugger is showing up either :-(
>>
>> Cheers,
>>    - Andreas
>>
>>
> It does end with terminateActive, but before that it calls activeController: , which spawns a new process (or it should,
> it is a primitive)

Yes, but if the old one is the process we want to debug, there is no 
point in terminating it, is there? After all it's the process that hit 
an error - we want to look at it, inspect it, step through it; not 
terminate it.

Cheers,
   - Andreas