Re: [Valgrind-developers] valgrind: r7080 - trunk/massif

2007-11-02 Thread Oswald Buddenhagen
On Fri, Nov 02, 2007 at 04:12:50AM +, [EMAIL PROTECTED] wrote: > Author: njn > -static UInt clo_heap_admin = 8; > + // clo_heap_admin is deliberately a word-sized type. At one point it was > + // a UInt, but this caused problems on 64-bit machines when it was > + // multiplied by a

Re: [Valgrind-developers] Alternative set of locking functions for thrcheck

2007-11-02 Thread Konstantin Serebryany
It works, many thanks! --kcc On 11/1/07, Julian Seward <[EMAIL PROTECTED]> wrote: > > On Thursday 01 November 2007 14:26, Konstantin Serebryany wrote: > > Hi Julian, > > > > What shall I do if my .so has no soname? > > What if my locking primitives reside in the main binary? > > That's ok. Use "

Re: [Valgrind-developers] can x86 valgrind run on a PPC client program?

2007-11-02 Thread Oswald Buddenhagen
On Fri, Nov 02, 2007 at 08:56:08AM -0700, Dave Nomura wrote: > Is it possible to run an x86 valgrind on a PPC program? If so, how > would you do it? > so you want a cross-executing valgrind ... while i think vex would have no major problems with it (give or take some minor adjustments), i'm prett

[Valgrind-developers] can x86 valgrind run on a PPC client program?

2007-11-02 Thread Dave Nomura
Is it possible to run an x86 valgrind on a PPC program? If so, how would you do it? -- Dave Nomura LTC Linux Power Toolchain - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find probl

[Valgrind-developers] valgrind: r7082 - in trunk: . massif

2007-11-02 Thread svn
Author: njn Date: 2007-11-02 20:44:57 + (Fri, 02 Nov 2007) New Revision: 7082 Log: Change ms_print to ms_print.in, link it into the build/install system. Added: trunk/massif/ms_print.in Removed: trunk/massif/ms_print Modified: trunk/configure.in trunk/massif/Makefile.am Modified

[Valgrind-developers] valgrind: r7083 - trunk/massif/perf

2007-11-02 Thread svn
Author: njn Date: 2007-11-02 20:47:53 + (Fri, 02 Nov 2007) New Revision: 7083 Log: Fix a Makefile issue that I think caused automated testing to fail on 'alvis' last night. I don't no why it worked on the other machines, must be an automake version thing. Modified: trunk/massif/perf/Makef

Re: [Valgrind-developers] valgrind: r7080 - trunk/massif

2007-11-02 Thread Nicholas Nethercote
On Fri, 2 Nov 2007, Oswald Buddenhagen wrote: > this is really odd ... That's what I thought :) > the code in update_heap_stats() did this: > (unsigned long) = (unsigned long) + (unsigned int) * (signed int); > while the actual multiplication is signed, the result is taken to be > unsigned and

Re: [Valgrind-developers] can x86 valgrind run on a PPC client program?

2007-11-02 Thread Nicholas Nethercote
On Fri, 2 Nov 2007, Dave Nomura wrote: > Is it possible to run an x86 valgrind on a PPC program? If so, how > would you do it? Maybe if you run Valgrind on QEMU (or another dynamic binary translator) running the PPC program? Otherwise I can't see how it would work. Nick -

Re: [Valgrind-developers] valgrind: r7080 - trunk/massif

2007-11-02 Thread Oswald Buddenhagen
On Sat, Nov 03, 2007 at 07:59:38AM +1100, Nicholas Nethercote wrote: > On Fri, 2 Nov 2007, Oswald Buddenhagen wrote: >> for *way* more clarity >> and less bloat i'd suggest writing the actual expression as >> update_alloc_stats(heap_szB_delta + >> (SizeT)clo_heap_admin*n_heap_blocks_delta); >> in

Re: [Valgrind-developers] can x86 valgrind run on a PP C client program?

2007-11-02 Thread Julian Seward
On Friday 02 November 2007 18:44, Oswald Buddenhagen wrote: > On Fri, Nov 02, 2007 at 08:56:08AM -0700, Dave Nomura wrote: > > Is it possible to run an x86 valgrind on a PPC program? If so, how > > would you do it? > > so you want a cross-executing valgrind ... > while i think vex would have no ma

[Valgrind-developers] valgrind: r7084 - trunk/massif

2007-11-02 Thread svn
Author: njn Date: 2007-11-02 21:44:02 + (Fri, 02 Nov 2007) New Revision: 7084 Log: Update todo notes Modified: trunk/massif/ms_main.c Modified: trunk/massif/ms_main.c === --- trunk/massif/ms_main.c 2007-11-02 20:47:53 U

[Valgrind-developers] Consistent naming options for output [was: Re: valgrind: r7084 - trunk/massif]

2007-11-02 Thread Josef Weidendorfer
On Friday 02 November 2007, [EMAIL PROTECTED] wrote: > Author: njn > +// - Massif out file: > +// default --> cachegrind.out. > +// --cg-out-file=X --> X. > +// --cg-out-file-exactly=X --> X > +//

[Valgrind-developers] 2007-11-03 02:00:01 CET nightly build (g5, SuSE 10.1, ppc970)

2007-11-02 Thread jseward
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-11-03 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

[Valgrind-developers] 2007-11-03 03:00:03 GMT nightly build (gill, x86_64, Fedora Core 2)

2007-11-02 Thread Tom Hughes
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-11-03 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

[Valgrind-developers] 2007-11-03 03:15:02 GMT nightly build (alvis, i686, Red Hat 7.3)

2007-11-02 Thread Tom Hughes
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-11-03 03:15:02 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... f

[Valgrind-developers] 2007-11-03 03:05:06 GMT nightly build (lloyd, x86_64, Fedora 7)

2007-11-02 Thread Tom Hughes
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-11-03 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

[Valgrind-developers] 2007-11-03 03:10:03 GMT nightly build (dellow, x86_64, Fedora 7)

2007-11-02 Thread Tom Hughes
Nightly build on dellow ( x86_64, Fedora 7 ) started at 2007-11-03 03:10:03 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... f