No debugger,��unfortunately. Although I really like Gofer, I also just used MC to build my image, with the same results. Is there someway to break into a locked image, and get a process browser or force a debugger to come up.

On Tue, Jan 12, 2010 at 15:43, St��phane Ducasse <stephane.ducasse@inria.fr> wrote:
> Download the 10506 Core image, and the tests pass there. So I installed the DEV environment, Glorp, Seaside, and my apps. These are all loaded via Gofer. Everything looks promising until, I do a Gofer commit, or just try to browse a repo with MC. CPUs at 99% and the image freezes.

We should really try to understand. Because there is nothing as bad as an image freeze.


> I'm having a hard time understanding how a tool like MC can shutdown the entire image, with no error message. None of the earlier Pharo builds were that unstable. I'm not reduced to filing out all my code changes, and saving them in Git.

can you get a debugger?

>
> On Tue, Jan 12, 2010 at 12:32, John Toohey <jt@parspro.com> wrote:
> Found the MC tests, and have 5 errors and 1 failure. All of them seem to be when its reading a file and gets an error in UUID>>fromString. I guess this is part of the problem that I am having.

Yes

>
>
> On Tue, Jan 12, 2010 at 12:05, John Toohey <jt@parspro.com> wrote:
> Not sure if this is what I have, I've just tried to save some code to my own repo, and although it seems like the code was updated, after MC puts the version info dialog on the screen, everything is frozen again. I still don't understand how the entire image can freeze over something like this.
>
>
> 2010/1/12 Mariano Martinez Peck <marianopeck@gmail.com>
> Ok....if this is your error, I am genius :)
>
> I found this issue: http://code.google.com/p/pharo/issues/detail?id=1293
>
> And then, I know you are using GlorpDBX......So, as I am developer, I know that the GlorpDBX loader, do this to load the fix to the underscore:
>
> �� �� (HTTPSocket httpGet: 'http://www.assembla.com/spaces/SqueakDBX/documents/dvVhPSvuCr3OqXeJe5aVNr/download/underscore.cs') readStream fileIn.
>
> So....maybe you are having that bug already reported.
>
> Sorry I don't have time to test it.
>
> Cheers
>
> Mariano
>
> 2010/1/12 John Toohey <jt@parspro.com>
>
> Rebuilt a new image from scratch, using the rc1 Core image, and everything was fine, until I did a "Save As" in order to rename the image. After that MC stops working again. Just completing another rebuild now, and will try to move the renamed image to another directory, before using MC again.
>
>
> 2010/1/12 Mariano Martinez Peck <marianopeck@gmail.com>
>
> And what about what I told you about reloading again the two versions?
>
> Sometimes I have problems with my proxy and I have to evaluate:
>
> HTTPSocket stopUsingProxyServer.
>
>
> 2010/1/11 John Toohey <jt@parspro.com>
> Did the cleanUpForRelease, but MC still hangs. Do you know what DEV image is the most stable right now, or is there a way to enable debug output from MC?
>
>
> 2010/1/11 Mariano Martinez Peck <marianopeck@gmail.com>
>
> Maybe you can reload the Monticello and MonticelloGUI package from the repository Pharo. However, I would check in that 10496 image which were the versions of those two packages and I would download exactly those two versions.
>
> Maybe you can also try to remove the package cache and also evaluate (backup the image first):
>
> �� �� MCFileBasedRepository flushAllCaches.
> �� �� MCMethodDefinition shutDown.
> �� �� MCDefinition clearInstances.
>
> Or even
>
> ScriptLoader new cleanUpForRelease
>
> Cheers
>
> Mariano
>
>
> 2010/1/11 John Toohey <jt@parspro.com>
> Hi,
> I've just built a new image based on PharoCore1.0rc1 Latest update: #10496, and MC freezes the image whenever I try to open a package. I can view a repo, but not open or load the packages. Is there anyway to rebuild MC, without rebuilding the entire image again? There is no debug file written out, just the CPU pegged at 99% and an unresponsive image.
>
> --
> -JT
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> -JT
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> -JT
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> -JT
>
>
>
>
>
> --
> -JT
>
>
>
>
>
> --
> -JT
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



--
-JT