Dear Shan More than a year has passed since the conversation below. We have a new release of valgrind (3) and callgrind (0.10.0) in the unstable archive of Debian now. Would you mind testing if the problem still persists?
Josef, is this really a problem of callgrind or is it a valgrind problem (if it still exists). Thanks for your help Philipp Am Tue, Sep 07, 2004 at 01:03:58AM +0200 hat Shan Mignot getippert: > I could install the debian packages all right tonight > valgrind_2.2.0-1_i386.deb > and valgrind-callgrind_0.9.9-1_i386.deb. Tried running it on the same > problematic case as previsouly and got: > > [EMAIL PROTECTED] ~/astro/Pyxis/tests > valgrind --tool=memcheck ./GD > BaadeDupli_ASM1_2x2.fits > ==917== Memcheck, a memory error detector for x86-linux. > ==917== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al. > ==917== Using valgrind-2.2.0, a program supervision framework for x86-linux. > ==917== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. > ==917== For more details, rerun with: -v > ==917== > ==917== warning: Valgrind's pthread_attr_destroy does nothing > ==917== your program may misbehave as a result > ==917== warning: Valgrind's pthread_attr_destroy does nothing > ==917== your program may misbehave as a result > ==917== warning: Valgrind's pthread_attr_destroy does nothing > ==917== your program may misbehave as a result > SNR1=1.40 SNR2=4.40 RON=13.90 BIAS=0.000000 > AL Margins : 17 337 > 2717 objects found. > ==917== warning: Valgrind's pthread_cond_destroy is incomplete > ==917== (it doesn't check if the cond is waited on) > ==917== your program may misbehave as a result > ==917== warning: Valgrind's pthread_cond_destroy is incomplete > ==917== (it doesn't check if the cond is waited on) > ==917== your program may misbehave as a result > ==917== warning: Valgrind's pthread_cond_destroy is incomplete > ==917== (it doesn't check if the cond is waited on) > ==917== your program may misbehave as a result > ==917== > ==917== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1) > ==917== malloc/free: in use at exit: 84 bytes in 2 blocks. > ==917== malloc/free: 75388 allocs, 75386 frees, 862809566 bytes allocated. > ==917== For a detailed leak analysis, rerun with: --leak-check=yes > ==917== For counts of detected errors, rerun with: -v > > Then: > > [EMAIL PROTECTED] ~/astro/Pyxis/tests > valgrind --tool=callgrind ./GD > BaadeDupli_ASM1_2x2.fits > ==899== Callgrind-0.9.9, a call-graph generating cache profiler for x86-linux. > ==899== Copyright (C) 2002-2004, and GNU GPL'd, by J.Weidendorfer, > N.Nethercote > et al. > ==899== Using valgrind-2.2.0, a program supervision framework for x86-linux. > ==899== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. > ==899== For more details, rerun with: -v > ==899== > ==899== warning: Valgrind's pthread_attr_destroy does nothing > ==899== your program may misbehave as a result > ==899== warning: Valgrind's pthread_attr_destroy does nothing > ==899== your program may misbehave as a result > ==899== warning: Valgrind's pthread_attr_destroy does nothing > ==899== your program may misbehave as a result > SNR1=1.40 SNR2=4.40 RON=13.90 BIAS=0.000000 > AL Margins : 17 337 > ==899== > ==899== Process terminating with default action of signal 11 (SIGSEGV) > ==899== Access not within mapped region at address 0xF30000C > ==899== at 0x3AA57282: (within /lib/libc-2.3.2.so) > ==899== by 0x3AA5607E: free (in /lib/libc-2.3.2.so) > ==899== by 0x8050691: CBodyList_GetElem (cbody_list.c:126) > ==899== > ==899== Events : Ir Dr Dw I1mr D1mr D1mw I2mr D2mr D2mw > ==899== Collected : 61922789 20257283 11701318 468962 279654 291491 6892 56128 > 57236 > ==899== > ==899== I refs: 61,922,789 > ==899== I1 misses: 468,962 > ==899== L2i misses: 6,892 > ==899== I1 miss rate: 0.75% > ==899== L2i miss rate: 0.1% > ==899== > ==899== D refs: 31,958,601 (20,257,283 rd + 11,701,318 wr) > ==899== D1 misses: 571,145 ( 279,654 rd + 291,491 wr) > ==899== L2d misses: 113,364 ( 56,128 rd + 56,128 wr) > ==899== D1 miss rate: 1.7% ( 1.3% + 2.4% ) > ==899== L2d miss rate: 0.3% ( 0.2% + 0.4% ) > ==899== > ==899== L2 refs: 1,040,107 ( 748,616 rd + 291,491 wr) > ==899== L2 misses: 120,256 ( 63,020 rd + 57,236 wr) > ==899== L2 miss rate: 0.1% ( 0.0% + 0.4% ) > zsh: segmentation fault valgrind --tool=callgrind ./GD > BaadeDupli_ASM1_2x2.fits > > cbody_list.c:126 frees previously allocated memory. Memcheck does not report > any > error there but this line clearly poses a problem to callgrind. As far as I > recall calltree used to segfault on a call to calloc, so the problem might be > somewhat different this time. If you have got any idea, any suggestion as to > tests that I may run, please don't hesitate, I'll gladly help. > > Thanks, > > Shan > > Selon Philipp Frauenfelder <[EMAIL PROTECTED]>: > > > Dear Shan > > > > There is a new stable release from upstream of valgrind and the > > calltree skin (now called callgrind) which are available in > > Debian now (well, we might have to wait a few days for callgrind > > as the package name has changed and I have just uploaded it). > > > > Could you please try if the bug is still there? > > > > Thanks -- Philipp | work: [EMAIL PROTECTED] +41 1 802 20 00 Frauenfelder | home: [EMAIL PROTECTED] +41 1 862 73 14 [PGP] | http://www.frauenfelder-kuerner.ch/ Proudly running Debian GNU/Linux. See http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
