|
From: Murali K. <mur...@gm...> - 2017-06-05 11:21:35
|
Hi, I tried to reproduce the same with the valgrind trunk code and the issue is not observed. Please are the observations from the executions. root@localhost:~$ uname -a Linux localhost 4.4.36-octeon-44-distro.git-v2.35-42-rc #1 SMP Thu Jun 1 07:15:54 UTC 2017 mips64 GNU/Linux root@localhost:~$ root@localhost:~$ /usr/bin/valgrind --version valgrind-3.13.0.SVN root@localhost:~$ root@localhost:~$ valgrind --tool=memcheck ls ==2617== Memcheck, a memory error detector ==2617== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2617== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==2617== Command: ls ==2617== ==2617== ==2617== HEAP SUMMARY: ==2617== in use at exit: 144 bytes in 3 blocks ==2617== total heap usage: 4 allocs, 1 frees, 32,960 bytes allocated ==2617== ==2617== LEAK SUMMARY: ==2617== definitely lost: 32 bytes in 2 blocks ==2617== indirectly lost: 112 bytes in 1 blocks ==2617== possibly lost: 0 bytes in 0 blocks ==2617== still reachable: 0 bytes in 0 blocks ==2617== suppressed: 0 bytes in 0 blocks ==2617== Rerun with --leak-check=full to see details of leaked memory ==2617== ==2617== For counts of detected and suppressed errors, rerun with: -v ==2617== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1) root@localhost:~$ Apart from the above mentioned ones, i have tried to execute the below command multiple times on the system without any issues observed. "valgrind --tool=memcheck --leak-check=full --show-reachable=yes --error-limit=no --log-file=log.txt ls -l /" Could you please share with us, what has included additionally to the trunk when compared to valgrind-3.12.0.tar.gz. Also please confirm if there is any possibility of getting these additional changes in the form of a patch so that i can use this officially. Thanks & Regards, Muralikrishna CH On Sat, May 27, 2017 at 8:41 PM, Murali Krishna <mur...@gm...> wrote: > Hi Rhys, > > Thanks for the info. > I will test the same with the in-development source and will update the > results soon. > > Thanks & Regards, > Muralikrishna CH > > On Sat, May 27, 2017 at 8:31 PM, Rhys Kidd <rhy...@gm...> wrote: > >> Hello, >> >> Based upon the output of valgrind --version provided you are using >> valgrind 3.12.0. >> >> Whilst this is indeed the most recently released version, the development >> team are well progressed through the next cycle. >> >> valgrind 3.13 is not yet released, however Petar was asking that you test >> the in-development code which we currently host on SVN. It may be that the >> bug you are experiencing is already fixed. >> >> Instructions to get and build the in-development source code version can >> be found here: >> >> http://valgrind.org/downloads/repository.html >> >> Best regards, >> Rhys >> >> >> On Sat, May 27, 2017 at 10:46 AM Murali Krishna <mur...@gm...> >> wrote: >> >>> Hi Petar, >>> >>> Thanks for the response. >>> As mentioned in my earlier email communication, valgrind version which >>> was running on my system and the latest one available(in the >>> valgrind.org) are same. >>> >>> Thanks & Regards, >>> Muralikrishna CH >>> >>> On Fri, May 26, 2017 at 4:38 PM, Petar Jovanovic <mip...@gm...> >>> wrote: >>> >>>> On Fri, May 26, 2017 at 10:48 AM, Murali Krishna >>>> <mur...@gm...> wrote: >>>> > Hi, >>>> > >>>> > As part of running the valgrind in our mips64 linux based system, we >>>> > observed couple of issues. >>>> > When tried to execute "ls" with valgrind, we see that the programme is >>>> > getting crashed. >>>> > >>>> Can you please try the latest SVN code and let us know if the problem >>>> occurs with it? >>>> >>>> Thanks. >>>> >>>> Regards, >>>> Petar >>>> >>> >>> >>> >>> -- >>> >>> Thanks & Regards, >>> Muralikrishna CH >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ >>> _________________________________________ >>> Valgrind-developers mailing list >>> Val...@li... >>> https://lists.sourceforge.net/lists/listinfo/valgrind-developers >>> >> > > > -- > > > > > Thanks & Regards, > Muralikrishna CH > > -- Thanks & Regards, Muralikrishna CH |