|
From: Dave N. <dc...@us...> - 2006-01-21 16:06:42
|
Julian Seward wrote:
>>I saw 23 failures on my test run of the latest PPC64 Valgrind I got from
>>the Code Repository. Most of the failures were the same as reported by
>>Julian but I was also seeing some additional failures:
>
>
> Ok. You should really compare against the latest nightly build on
> Ceri's 970 (g5) which is posted to this list every night. Since there's
> been a lot of ppc hacking this last week, the test results have
> changed rapidly the past few days.
>
>
>>Here is my debugging analysis of the problem. Unless I have made a
>>mistake in locating the correct #includes/#defines I don't see anything
>>that looks host dependent.
>>
>>! valgrind: m_coredump/coredump-elf.c:267 (fill_prstatus): Assertion
>>'sizeof(*regs) == sizeof(prs->pr_reg)' failed.
>>[...]
>
>
> Good that you found that. But .. can you clarify which particular
> test is causing this failure, and what V version (3.1.0 or the svn
> trunk). It's not clear from your message.
>
> J
>
Here is what I wrote in my initial message:
>I saw 23 failures on my test run of the latest PPC64 Valgrind I got
>from the Code Repository. Most of the failures were the same as
>reported by Julian but I was also seeing some additional failures:
>memcheck/tests/badjump
>memcheck/tests/describe-block
>memcheck/tests/match-overrun
>none/tests/async-sigs
>none/tests/blockfault
>
>I saw the same failures when running the Valgrind 3.1.0 release.
The assertion error occurred in the list of tests listed above in a run
against an SVN snapshot taken on 1-18, as well as on the offical
Valgrind 3.1.0 release.
This list of failures was obtained by comparing my test results with
those posted on the mailing list on 1-19
Could you answer a couple of other unrelated questions?
1. if I installed valgrind into /usr/local but want to run a newer SVN
version against some program is it sufficient to invoke valgrind:
<SVN dir>/coregrind/valgrind <my_program>
or
alias vg <SVN dir>/coregrind/valgrind
vg <my_program>
I know that there are other libraries/shared objects that valgrind
accesses and I thought that it might depend on the path used to
invoke
valgrind. If I use the VALGRIND_LAUNCHER or VALGRIND_LIB variables
(set to a different valgrind release) for debugging but forget to
unset them am I at risk for possibly
running a different version of valgrind than I intended?
2. I've been using the svn command listed on your website to pull over a
newer version of valgrind. This command pulls over the entire
trunk/* tree. Is there a way to just incrementally pull the files
that changed or is the granularity of SVN just the entire source
tree?
|