|
From: Dave N. <dc...@us...> - 2005-11-09 22:15:31
|
I recently downloaded the valgrind 3.0.1 tarball and installed on an IBM ppc64 machine to check out where things stand on the ppc32 and have a number of questions. 1. Should I be seing a majority of passes in the valgrind test suite? I was seeing 70% failures but I thought it might be due to some sort of pilot error on my part. 2. I tried downloading from the Code Repository for the 3.0 development line. I tried to just autoconf/automake/configure... this but it seems that all of the build machinery wasn't in this download as opposed to the 3.0.1 tarball. Is this expected behavior? Was I just supposed to integrate these changes into my own copy of the source line before attempting to build it? 3. I noticed that there were some pretty significant changes in this code from the 3.0.1 tarball. e.g. the stage2 program no longer even exists. I did manage to build it after integrating the changes into the build area I had set up from the 3.0.1 tarball and got 30% failures in the test suite so this looked like progress. Can you tell me what I downloaded? Are these just source changes since 3.0.1 was released? Do these include the work that has gone into the upcoming 3.1 release? When is the 3.1 release going to happen? 4. I noticed in some of the postings in this mailing list that there were some items involving ppc64 ptrace. Is there any ongoing work on porting valgrind to ppc64? If there is, I would be interested in hearing about it. Thanks for any answers to these questions that you can give me. I'm just trying to learn my way around valgrind and OpenSource development. Any help/suggestions you can give would be greatly appreciated. |