Stef, I have an idea for something that might be simple enough to make the point. It is confusing though, especially that once an image goes bad, it stays bad, even though (AFAIK, I don't save it after the damage is done). I have work to do there. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Friday, February 10, 2012 3:29 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins On Feb 9, 2012, at 11:39 PM, Schwab,Wilhelm K wrote:
Sven,
Fair enough, but the game plan is for people to use Metacello configurations to load what they need to build an image. I am attempting to do just that, and am reporting (rather negative so far) experience, with debug logs.
Sure we will start to work on distribution certification as I mentioned in the draft of Pharo Vision document which escape my hd recently.. new version coming soon. Bill can you post a reproachable case for us to play with?
Pharo's fault or not, something is broken. But if Pharo is going to send users into the current state of Metacello, the weather around the lighthouse is going to be grim.
Interesting ideas about the package cache being damaged. Maybe the logs will reveal something??
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven@beta9.be] Sent: Thursday, February 09, 2012 5:14 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins
On 09 Feb 2012, at 22:27, Schwab,Wilhelm K wrote:
My new 1.4 image is behaving a *little* better than its predecessors, but there is still a problem. It seems to happen after invoking Metacello loads, even with the mirror. Odd behaviors include:
(1) can't open debugger (2) can't open process browser (3) intermittent flashing/alternating cursors in text editors.
Whatever happens, it seems to be saved into the image as MC works, because killing the image and reloading results in a hobbled system.
At least with 1.4, I can sometimes break into a debugger, presumably because something is busy in a tight loop. That might be a/the parser??
BTW, in an hour (max) of playing around, I've generated a 38 MB debug log - too big to read :( There are mentions of a parser, but my grep creativity has not allowed me to pull out any useful information. Perhaps I can start over with a clean log, let it get into some trouble, and review the log at a smaller size.
Suggestions?
Some remarks:
- if you load code and it fails for whatever reason, and there was no hidden save somewhere, I would be extremely surprised if killing the image (clean or otherwise) would result in permanent damage; the only side effect could be in your filesystem (local package cache), but even that would normally not hurt the image itself
- you are obviously loading lots of stuff: when this does not work, that is not 'Pharo's fault', you should ask the people who wrote these libraries for help (maybe through this list); you can't call gcc crap or unstable when a certain library fails
- when you are reporting bugs and ask for help, you really have to bring your problem down to a simple test case that others can reproduce; even if people would want to help you, they cannot do so with these generalizations
Sven