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

Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-12-20 03:15:12 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-12-20 03:05:06 GMT nightly build (lloyd, x86_64, Fedora 7)

Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-12-20 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-12-20 03:10:04 GMT nightly build (dellow, x86_64, Fedora 8)

Nightly build on dellow ( x86_64, Fedora 8 ) started at 2007-12-20 03:10:04 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] valgrind and huge (>1GB) bss sections

Hello I am trying to run valgrind on the program zeusmp from the SPEC CPU2006 benchmark suite. $ valgrind ./zeusmp.static valgrind: mmap(0x811, 1172246528) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

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

Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-12-20 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 .

[Valgrind-developers] basic block vector plugin

Hello I've updated my Simpoint Basic Block Vector generating plugin to work with Valgrind 3.3.0 http://www.csl.cornell.edu/~vince/projects/valsim/ I was wondering what the criteria are for becoming an official experimental plugin that is included in the main valgrind tree. I'd be willing to m

Re: [Valgrind-developers] [Valgrind-users] Valgrind memcheck and std map and array array bounds checking

On Wed, 19 Dec 2007, Sahni, Jitan wrote: > is there any way in memcheck to detect out of bound array access, when > using stl objects like std::string and std::map ? Recently I had once such > bug and took me about 10 days with valgrind before it pin pointed me to > exact error line and I think

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

Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-12-20 02:00:01 CET Results differ from 24 hours ago Checking out valgrind source tree ... failed Last 20 lines of verbose log follow echo Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {200

Re: [Valgrind-developers] valgrind: r7274 - in trunk: . memcheck memcheck/tests

On Sunday 16 December 2007, Nicholas Nethercote wrote: > I didn't know about the 'deprecated' attribute, thanks for the tip. In > this case, I don't think we could have used it because they were macros. I think it would be possible to convert them into static inlines though. > These macros we

[Valgrind-developers] valgrind: r7303 - trunk/memcheck/tests

Author: sewardj Date: 2007-12-19 11:01:13 + (Wed, 19 Dec 2007) New Revision: 7303 Log: Add a couple of regtests for large stack frame management. Added: trunk/memcheck/tests/lsframe1.c trunk/memcheck/tests/lsframe1.stderr.exp trunk/memcheck/tests/lsframe1.stdout.exp trunk/memcheck