Re: [Valgrind-users] suppression help?

2009-02-05 Thread Ashley Pittman
[sending again ccing the list this time] 2009/2/4 Meseret Gebre > Greetings, > > I have a simple mpi program, please find it attached. > I am using valgrind-3.3.0 > > I run my code with the following command: > mpiexec -n 2 valgrind --gen-suppressions=yes ./mpitest --gen-suppressions=all is

[Valgrind-users] valgrind AIX 5.3 64bit on big big software

2009-02-05 Thread denis joubert
Hello, On a very big software we develop on AIX 5.3 I got this error after trying to increase --main-stackssize at 13300 (because previous similar errors) but with a smaller software (very very small) i have the same error, is it because i use xlc 9.0 as compiler ? ==7237910== Process terminat

[Valgrind-users] Pthread error not detected by DRD and Helgrind

2009-02-05 Thread Christoph Bartoschek
Hi, today I had to learn that the attached program is incorrect. It is not allowed to destroy the barrier while not all threads have left the pthread_barrier_wait() call. Unfortunately neither DRD nor Helgrind warn about this error. Could you please improve the tools to detect such errors? Chr

Re: [Valgrind-users] Pthread error not detected by DRD and Helgrind

2009-02-05 Thread Julian Seward
On Thursday 05 February 2009, Christoph Bartoschek wrote: > Hi, > > today I had to learn that the attached program is incorrect. It is not > allowed to destroy the barrier while not all threads have left the > pthread_barrier_wait() call. > > Unfortunately neither DRD nor Helgrind warn about this e

Re: [Valgrind-users] valgrind AIX 5.3 64bit on big big software

2009-02-05 Thread Julian Seward
First of all, are you able to compile and run (on Valgrind) any simple program (eg, hello world), in 64-bit mode? J > ==7237910== Process terminating with default action of signal 11 (SIGSEGV): > dump > ing core > ==7237910== Access not within mapped region at address 0xFFFE > ==723

Re: [Valgrind-users] Pthread error not detected by DRD and Helgrind

2009-02-05 Thread Christoph Bartoschek
Am Donnerstag, 5. Februar 2009 schrieb Julian Seward: > On Thursday 05 February 2009, Christoph Bartoschek wrote: > > Hi, > > > > today I had to learn that the attached program is incorrect. It is not > > allowed to destroy the barrier while not all threads have left the > > pthread_barrier_wait()

Re: [Valgrind-users] Pthread error not detected by DRD and Helgrind

2009-02-05 Thread tom fogal
Christoph Bartoschek writes: > Am Donnerstag, 5. Februar 2009 schrieb Julian Seward: > > On Thursday 05 February 2009, Christoph Bartoschek wrote: > > > Hi, > > > > > > today I had to learn that the attached program is incorrect. It is not > > > allowed to destroy the barrier while not all threads

Re: [Valgrind-users] Pthread error not detected by DRD and Helgrind

2009-02-05 Thread Christoph Bartoschek
Am Donnerstag, 5. Februar 2009 schrieb tom fogal: > I'm getting a bit off topic, but .. > > Perhaps I'm just not understanding the linked-to discussion, but given > this interpretation -- how could one ever delete a barrier? > > It sounds like the only safe way to destroy the barrier is if you've

[Valgrind-users] Treating memory leaks as "errors"

2009-02-05 Thread Vikas Rangarajan
Valgrind does not consider memory leaks to be errors. e.g.: valgrind --leak-check=full --error-exitcode=1 ./a.out ==13671== ==13671== 38 (8 direct, 30 indirect) bytes in 1 blocks are definitely lost in loss record 1 of 2 ==13671==at 0x4A06019: operator new(unsigned long) (vg_replace_malloc.c:1

[Valgrind-users] valgrind 3.3.0 and db-attach

2009-02-05 Thread wim . delvaux
Hi all, When I run valgrind like : valgrind --suppressions=/home/u19809/valgrind.supp --db-attach=yes --num-callers=20 and when asked to attach to the debugger I say 'y' I get this ... ==6488==by 0x5951D4B: Wrap_QTA_Run(Instance_S*, Instance_S*, AC_Variant_S*) (QtApp.c:231) ==6488==b