|
From: Julian S. <js...@ac...> - 2002-11-19 23:58:51
|
> > Yesterday afternoon I ran KDE-3.1-rc3 on addrcheck. This is the entire > > process tree starting from startkde. It pretty much worked, but was a > > bit slow and one process bombed valgrind. All output was logged to a > > different machine running the listener. > > Wow that sounds great. How have things come since Monday? Are your > scripts and tools for this all packaged up? No, but we can do 'make dist' and write a half-page README if you want to try it. I found that valgrind bombed once during the previous session, and I wanted to track it down. + we are not in a total hurry to release it. But as I say, I am very happy to make you a snapshot tarball (version 1.9.1) if you want. > It would be nice to see those Arts errors too. Arts has lots of memory > problems on PPC architecture apparently. Attached. I don't think they are particularly interesting. I'm not using artsd for anything. After startup I get a box saying "Sound server CPU overload" or something like that; when I clicked OK the attached gunk came out. I tried to find all lines in the log for this process (5805) but I am not sure why the startup stuff is missing; that would tell us exactly what's running. Note, this is with RC3; I haven't scagged RC4 yet. > It really seems that my testing suggestion is far too late for 3.1.0, but > I'd like to start formalising it for 3.2.0. You are doing a Good Thing here, and you have my encouragement. J |