Le 06/09/2012 16:31, [email protected] a écrit :
Main UI process and a haltOnce would indeed be great instead of the current kata.
I'd be a lot safer if I could "trace" the main UI process instead of blocking it.
Maybe block it, kill it (keep the stack) and restart a new one immediately (in a safe UI context with say just the debugger open) so that I can explore the current state and eventually let it proceed.
-- Remote debug from another Pharo image ? Thierry
2012/9/6 Goubier Thierry <[email protected] <mailto:[email protected]>> Le 06/09/2012 16:16, Sean P. DeNigris a écrit : Alexandre Bergel-7 wrote Ok, this is indeed the first thing you want On Sep 5, 2012, at 7:51 PM, phil@ wrote: An ability to jump to the process code right away. Yes, that would be super cool! Isn't that the case in the current process browser ? Or do you mean something like forcing a breakpoint in a currently running process ? ( It would be cool to breakpoint like that the main UI process... :)). Thierry -- View this message in context: http://forum.world.st/Process-__browser-next-generation-__tp4646267p4646408.html <http://forum.world.st/Process-browser-next-generation-tp4646267p4646408.html> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
