Author: njn
Date: 2007-11-12 07:05:07 + (Mon, 12 Nov 2007)
New Revision: 7153
Log:
Another attempt at fixing some Massif regtest failures.
Modified:
trunk/massif/tests/culling1.stderr.exp
trunk/massif/tests/culling2.stderr.exp
trunk/massif/tests/deep-B.stderr.exp
trunk/massif/test
John Reiser writes:
> > It's now used as the TLS pointer. It should get initialized for the
> > main thread in glibc, and for other threads by the clone() system
> > call. ...
>
> Please give a citation to a reference for this change.
I think it's described in the LSB psABI for 32-bit powerpc.
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-11-12 03:05:06 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... fa
Nightly build on dellow ( x86_64, Fedora 7 ) started at 2007-11-12 03:10:07 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... f
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-11-12 03:00:02
GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests .
Paul Mackerras wrote:
> Julian Seward writes:
>
>
>>complaining that r2 contains an undefined value. ...
>
> It's now used as the TLS pointer. It should get initialized for the
> main thread in glibc, and for other threads by the clone() system
> call. ...
Please give a citation to a reference
Julian Seward writes:
> complaining that r2 contains an undefined value. And it's true;
> it is not written at all in the procedure in which this is
> reported. Which is odd. AFAIK r2 is not an argument register
> and it didn't used to have any particular meaning in the ppc32 ELF
> ABI.
It's n
I've been testing Valgrind on a recent ppc distro, openSUSE 10.3
running on a 32-bit ppc box. Memcheck generates huge numbers of
undefined value errors even for the simplest program (eg /bin/date)
and I'm trying to figure out what's going on.
Many of the errors seem to relate to load instruction
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-11-12 02:00:01 CET
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... fail
Author: njn
Date: 2007-11-12 01:16:24 + (Mon, 12 Nov 2007)
New Revision: 7152
Log:
Fix verbose output filtering for Massif.
Modified:
trunk/massif/tests/filter_verbose
Modified: trunk/massif/tests/filter_verbose
===
--- trun
Author: sewardj
Date: 2007-11-12 01:01:08 + (Mon, 12 Nov 2007)
New Revision: 7151
Log:
More glibc-2.6 suppressions.
Modified:
trunk/glibc-2.3456-NPTL-helgrind.supp
Modified: trunk/glibc-2.3456-NPTL-helgrind.supp
===
--- trun
> Helgrind: Fatal internal error -- cannot continue.
> Helgrind: mk_SHVAL_ShR(tset=8192,lset=1): FAILED
> Helgrind: max allowed tset=8191, lset=131071
> Helgrind: program has too many thread sets or lock sets to track.
Yes. It's a problem I'm tracking. Really it is trying to squeeze
too much in
I am trying to use helgrind and so far I have a showstopper.
Simplified, my software is a number of servers and clients. The
clients execute a heartbeat connection to one server (1/sec).
Bringing up the servers and clients all looks fine but very soon
(90s after it actually starts running) one se
Author: njn
Date: 2007-11-11 22:15:58 + (Sun, 11 Nov 2007)
New Revision: 7150
Log:
- Make other integer CLO macros more correct, as I did for VG_NUM_CLO in the
last commit.
- Add a VG_DBL_CLO for fractional arguments.
- Make Massif's --threshold and --peak-inaccuracy arguments fractional.
M
Author: njn
Date: 2007-11-11 21:58:21 + (Sun, 11 Nov 2007)
New Revision: 7149
Log:
Add four 'strtoll' variants, which are like 'atoll' but let you detect if
the string converted wasn't entirely numeric. Using them for numeric
command-line options -- previously if you had a option "--foo=", wh
On Sun, 11 Nov 2007, Bart Van Assche wrote:
> Is any other Valgrind developer using openSUSE 10.3 ? Many regression
> tests that run fine during the nightly build fail on openSUSE 10.3. I
> don't know whether this is due to changes in Valgrind or due to
> changes in gcc, binutils or glibc.
>
>
> $
Author: njn
Date: 2007-11-11 21:12:28 + (Sun, 11 Nov 2007)
New Revision: 7148
Log:
Add some seemingly unnecessary initialisations to shut GCC 4.0.2 up.
Modified:
trunk/helgrind/hg_main.c
Modified: trunk/helgrind/hg_main.c
==
> Is any other Valgrind developer using openSUSE 10.3 ? Many regression
> tests that run fine during the nightly build fail on openSUSE 10.3.
> == 350 tests, 66 stderr failures, 50 stdout failures, 0 post failures ==
On openSUSE 10.3 running on x86_64 I get this:
== 350 tests, 12 stderr failure
Author: sewardj
Date: 2007-11-11 18:56:39 + (Sun, 11 Nov 2007)
New Revision: 7147
Log:
In vg_SP_update_pass (stack-pointer-change analysis code), correctly
handle partial updates of SP. Tricky. This fixes #152022.
Modified:
trunk/coregrind/m_translate.c
Modified: trunk/coregrind/m_tran
A new drd version is available at the following location:
http://home.euphonynet.be/bvassche/valgrind/valgrind-7146-drd-2007-11-11.patch.gz
Changes compared to version 2007-02-27:
- The patch now works with the latest Valgrind source code (SVN
trunk), that is, after thrchk was merged to the trunk.
Hello,
Is any other Valgrind developer using openSUSE 10.3 ? Many regression
tests that run fine during the nightly build fail on openSUSE 10.3. I
don't know whether this is due to changes in Valgrind or due to
changes in gcc, binutils or glibc.
$ svn update
Fetching external item into 'VEX'
Ex
21 matches
Mail list logo
