valgrind-users — General discussion list for Valgrind users

Re: [Valgrind-users] Problem in getting valgrind to run on android

[Vignesh <mv...@ya...>]

Thank you for your clues.

Few dynamically loaded libraries were statically linked to few other libraries.   After converting them to dynamic libraries, I am closer to detect memory problems.   Also, I had to turn on -g and avoid stripping the executable to get an accurate detection

However, this still dazzles me:

I still get this warning while running valgrind:
--8925--   Considering /system/lib/libc.so ..
--8925--   .. CRC mismatch (computed aedb52cb wanted eadc3e5a)
--8925--    object doesn't have a symbol table

When I compute crc for /system/lib/libc.so externally, I get aedb52cb and the system under test doesn't contain libc anywhere else..  Where else is the executable picking libc from?  Output of strace relevant to libc given below

open("/vendor/lib/libc.so", O_RDONLY)   = -1 ENOENT (No such file or directory)
open("/system/lib/libc.so", O_RDONLY)   = 3
open("/vendor/lib/libc.so", O_RDONLY)   = -1 ENOENT (No such file or directory)
open("/system/lib/libc.so", O_RDONLY)   = 3
readlink("/proc/self/fd/3", "/system/lib/libc.so", 4096) = 19
stat64("/system/lib/libc.so", {st_mode=S_IFREG|0666, st_size=310652, ...}) = 0
readlink("/proc/self/fd/3", "/system/lib/libc.so", 4096) = 19
stat64("/system/lib/libc.so", {st_mode=S_IFREG|0666, st_size=310652, ...}) = 0
readlink("/proc/self/fd/3", "/system/lib/libc.so", 4096) = 19
stat64("/system/lib/libc.so", {st_mode=S_IFREG|0666, st_size=310652, ...}) = 0
--9086-- Reading syms from /system/lib/libc.so
open("/system/lib/libc.so", O_RDONLY)   = 4
readlink("/proc/self/fd/4", "/system/lib/libc.so", 4096) = 19
open("/system/lib/libc.so", O_RDONLY)   = 4
--9086--   Considering /system/lib/libc.so ..
readlink("/proc/self/fd/4", "/system/lib/libc.so", 4096) = 19
open("/system/lib/.debug/libc.so", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/debug/system/lib/libc.so", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/data/local/symbols/system/lib/libc.so", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/sdcard/symbols/system/lib/libc.so", O_RDONLY) = -1 ENOENT (No such file or directory)
--9086:1:aspacem  ( 4) /system/lib/libc.so
--9086-- Caught __NR_exit; running __libc_freeres()

Thank you,
Vignesh


On Tuesday, 27 May 2014, 19:01, John Reiser <jr...@Bi...> wrote:
 


> --16527--   Considering /system/lib/libc.so ..
> --16527--   .. CRC mismatch (computed aedb52cb wanted eadc3e5a)
> --16527--    object doesn't have a symbol table

The checksums mismatch, so memcheck ignores the symbols [if there are any.]
Therefore 'malloc' and 'free' cannot be found.
Most often this is a clue that the software on the target machine
is not installed properly.  Run "strace  -f  -e  trace=file  valgrind  ..."
and see exactly which files memcheck wants.  Look at all files
that are reported by strace whose names contain the substring "libc",
and determine what kind of symbol tables they contain: SHT_SYMTAB,
DT_SYMTAB (with DT_HASH or DT_GNU_HASH).  Figure out why the
CRC mismatches.  Check version numbers, date-last-modified ("ls -l"), etc.
Compare output of "readelf --all <filename>" for all candidates.
Install the correct file(s) so that the message
"CRC mismatch" no longer appears.




------------------------------------------------------------------------------
The best possible search technologies are now affordable for all companies.
Download your FREE open source Enterprise Search Engine today!
Our experts will assist you in its installation for $59/mo, no commitment.
Test it for FREE on our Cloud platform anytime!
http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Re: [Valgrind-users] Valgrind Multi-threads

[Tom H. <to...@co...>]

On 30/05/14 10:08, Domingues Luis Filipe wrote:

> When instrumenting multi-threaded programs, how Valgrind manage it?
> Did it do the instrumentation in a single thread, or is it
> multi-threaded on instrumentation time?

http://www.valgrind.org/docs/manual/manual-core.html#manual-core.pthreads

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/

[Valgrind-users] Valgrind test programs

[Domingues L. F. <Lui...@ed...>]

Hello,

I want to test a tool I build, but I want to know if they are some
references programs to tests Valgrind tools.

Regards,
Luis Domingues 

[Valgrind-users] Valgrind Multi-threads

[Domingues L. F. <Lui...@ed...>]

Hello,

When instrumenting multi-threaded programs, how Valgrind manage it?
Did it do the instrumentation in a single thread, or is it
multi-threaded on instrumentation time?

Regards,
Luis Domingues

Re: [Valgrind-users] top and massif about jack2 memory usage

[Maurice v. S. <ma...@bl...>]

Valgrind doesn't track memory allocation through mmap, mremap and brk. 

You can use massif with the option --pages-as-heap=yes to track those instead of malloc etc. 

][ Maurice van Swaaij ][ 

----- Original Message -----

| From: "Leonardo Gabrielli" <l.g...@un...>
| To: val...@li...
| Sent: Thursday, May 29, 2014 12:50:52 PM
| Subject: [Valgrind-users] top and massif about jack2 memory usage

| Dear all,
| I'm looking into valgrind + massif, to track down where the massive
| memory requirements of jackdmp (Jack2) come from.
| I'm new to its usage and perhaps I miss something regarding memory
| attribution with the top command, but here's what I face:
| According to top, jackd takes 216Mb VIRT, 147M RES, 96Mb SH.
| If I run with valgrind --tool=massif the log I get from massif is a
| mere
| 6Mb of memory. Either valgrind is right and I do not know what the
| top
| figures are about, either valgrind can't track down all that large
| memory locked by jack. According to my knowledge jack is used to get
| slightly less than 100MB, so I guess the second is the most probable
| answer.

| FYI: Jack runs with 4 threads, one of which is in a privileged PAM
| group
| with unlimited memory locking and realtime (SCHED_FIFO) priority.

| Maybe massif can't see the thread which allocates most of the memory?

| Regards

| Leonardo

| --

| Dr. Leonardo Gabrielli, PhD student
| A3Lab - Dept. Information Engineering
| Università Politecnica delle Marche
| via Brecce Bianche 12, 60131, Ancona, Italy
| Skype: leonardo.gabrielli
| Web: a3lab.dii.univpm.it/people/leonardo-gabrielli
| <http://a3lab.dii.univpm.it/people/leonardo-gabrielli>

| ------------------------------------------------------------------------------
| Time is money. Stop wasting it! Get your web API in 5 minutes.
| www.restlet.com/download
| http://p.sf.net/sfu/restlet
| _______________________________________________
| Valgrind-users mailing list
| Val...@li...
| https://lists.sourceforge.net/lists/listinfo/valgrind-users

[Valgrind-users] top and massif about jack2 memory usage

[Leonardo G. <l.g...@un...>]

Dear all,
I'm looking into valgrind + massif, to track down where the massive 
memory requirements of jackdmp (Jack2) come from.
I'm new to its usage and perhaps I miss something regarding memory 
attribution with the top command, but here's what I face:
According to top, jackd takes  216Mb VIRT, 147M RES, 96Mb SH.
If I run with valgrind --tool=massif the log I get from massif is a mere 
6Mb of memory. Either valgrind is right and I do not know what the top 
figures are about, either valgrind can't track down all that large 
memory locked by jack. According to my knowledge jack is used to get 
slightly less than 100MB, so I guess the second is the most probable answer.

FYI: Jack runs with 4 threads, one of which is in a privileged PAM group 
with unlimited memory locking and realtime (SCHED_FIFO) priority.

Maybe massif can't see the thread which allocates most of the memory?

Regards

Leonardo

-- 

Dr. Leonardo Gabrielli, PhD student
A3Lab - Dept. Information Engineering
Università Politecnica delle Marche
via Brecce Bianche 12, 60131, Ancona, Italy
Skype: leonardo.gabrielli
Web: a3lab.dii.univpm.it/people/leonardo-gabrielli 
<http://a3lab.dii.univpm.it/people/leonardo-gabrielli>

Re: [Valgrind-users] Valgrind ignores --tool in VALGRIND_OPTS env var and .valgrindrc?

[Philippe W. <phi...@sk...>]

On Wed, 2014-05-28 at 16:08 +0200, Ishwara wrote:
> Hi
> I'm new to valgrind. I wanted to change a default tool to e.g. helgrind by setting VALGRIND_OPTS env variable.
> echo $VALGRIND_OPTS prints: --log-file=rrc.log --time-stamp=yes --tool=helgrind
> But valgrind keeps running memcheck. Other arguments work, only tool is being ignored.
> I get the same result when using .valgrindrc file.
> Anyone has any idea how to change the default tool? (not specifying it each time)
Some options cannot be specified in VALGRIND_OPTS.
The reason is that the command line processing is done in two phases:
  a subset of the options is "pre-checked" (either by the launcher
        or by the tool itself)
  the rest of the options is parsed in a second phase.


The following options are determined during the first phase,
(without looking at ~/.valgrindrc, $VALGRIND_OPTS and ./.valgrindrc) :
--tool=
--command-line-only=
-d
--max-stackframe=
--main-stacksize=
--sim-hints=
--profile-heap=
--core-redzone-size=
--redzone-size=
--aspace-minaddr=


The (main) reason for this is that processing .valgrindrc and others
implies to have some parts of Valgrind initialised (e.g. the memory
management). And the initialisation of these parts implies to
have the value of the above arguments.
In summary, chicken and egg problem.

This could probably be fixed/changed by having the launcher
expanding .valgrindrc/VALGRIND_OPTS/... and inserting it into a new argv vector
before exec-ing the tool file.
Looks a nice small first change to try in valgrind, if you are interested :)

(the only possible difficulty I see is to avoid re-inserting these args
in case of a child process)

Philippe

[Valgrind-users] Valgrind ignores --tool in VALGRIND_OPTS env var and .valgrindrc?

[Ishwara <is...@sz...>]

Hi
I'm new to valgrind. I wanted to change a default tool to e.g. helgrind by setting VALGRIND_OPTS env variable.
echo $VALGRIND_OPTS prints: --log-file=rrc.log --time-stamp=yes --tool=helgrind
But valgrind keeps running memcheck. Other arguments work, only tool is being ignored.
I get the same result when using .valgrindrc file.
Anyone has any idea how to change the default tool? (not specifying it each time)

[Valgrind-users] How to disassociated a memory block with the system heap

[Phil L. <plo...@sa...>]

In my application, I have a pool of memory which is allocated from the system heap, then stored in a linked list.  I have used VALGRIND_CREATE_MEMPOOL and other annotations to tell memcheck about the memory pool and which memory blocks have been allocated from it, so that usage and access errors can be reported in terms of the memory pool.

My problem is that the particular linked list implementation ends up using an interior pointer.  What I'm finding is that when I shut down, I get "memory may be lost" errors for all of the blocks which are on the memory pool linked list.  Is there an annotation I can use to disassociate the memory block from the system heap so that it is only associated with the linked-list memory pool?

Phil
-----
Phil Longstaff
Senior Software Engineer
x2904

Re: [Valgrind-users] Problem in getting valgrind to run on android

[John R. <jr...@Bi...>]

> --16527--   Considering /system/lib/libc.so ..
> --16527--   .. CRC mismatch (computed aedb52cb wanted eadc3e5a)
> --16527--    object doesn't have a symbol table

The checksums mismatch, so memcheck ignores the symbols [if there are any.]
Therefore 'malloc' and 'free' cannot be found.
Most often this is a clue that the software on the target machine
is not installed properly.  Run "strace  -f  -e  trace=file  valgrind  ..."
and see exactly which files memcheck wants.  Look at all files
that are reported by strace whose names contain the substring "libc",
and determine what kind of symbol tables they contain: SHT_SYMTAB,
DT_SYMTAB (with DT_HASH or DT_GNU_HASH).  Figure out why the
CRC mismatches.  Check version numbers, date-last-modified ("ls -l"), etc.
Compare output of "readelf --all <filename>" for all candidates.
Install the correct file(s) so that the message
"CRC mismatch" no longer appears.

Re: [Valgrind-users] setns syscall with valgrind

[Himanshu S <mai...@gm...>]

John, Thanks for the response. We are using 64-bit x86 Linux. As such setns
switches the network name space context to the one where the 'fd' in the
argument is referring. I will try your suggestion and let you know.


On Fri, May 23, 2014 at 6:14 PM, John Reiser <jr...@bi...> wrote:

> > In our code we use setns system call. [In] valgrind version (3.8.1), it
> seems like this syscall is not handled.
> >
> >
> > --2726-- WARNING: unhandled syscall: 308
> > --2726-- You may be able to write your own handler.
> > --2726-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
> > --2726-- Nevertheless we consider this a bug.  Please report
> > --2726-- it at http://valgrind.org/support/bug_reports.html.
>
>
> Version 3.9.0 was released about 7 or 8 months ago.  Why not upgrade?
>
> You should tell us which hardware architecture and which operating system.
>
> Because the setns system call:
>         int setns(int fd, int nstype);
> does not reference memory, then setns is a no-operation as far as memcheck
> is concerned.
> Write an empty subroutine and put its address into the table:
>         static SyscallTableEntry syscall_table[] = { ... };
> Then submit your patch at the indicated URL.
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>

Re: [Valgrind-users] Problem in getting valgrind to run on android

[Vignesh <mv...@ya...>]

Hi,

I am still facing troubles getting a valgrind report on an android phone (armv7-a-neon) after changing my executable to be a dynamically loaded executable.

I am not very sure, if I understand the output of the following.   

......
......--16527:1:main     Starting the address space manager--16527:2:aspacem            sp_at_startup = 0x00be9419a0 (supplied)
--16527:2:aspacem                  minAddr = 0x0004000000 (computed)
--16527:2:aspacem                  maxAddr = 0x00be940fff (computed)
--16527:2:aspacem                   cStart = 0x0004000000 (computed)
--16527:2:aspacem                   vStart = 0x00614a1000 (computed)
--16527:2:aspacem    suggested_clstack_top = 0x00bd941fff (computed)
--16527:2:aspacem    <<< SHOW_SEGMENTS: Initial layout (5 segments, 0 segnames)
--16527:2:aspacem      0: RSVN 0000000000-0003ffffff     64m ----- SmFixed
--16527:2:aspacem      1:      0004000000-00614a0fff   1492m
--16527:2:aspacem      2: RSVN 00614a1000-00614a1fff    4096 ----- SmFixed
--16527:2:aspacem      3:      00614a2000-00be940fff   1492m
--16527:2:aspacem      4: RSVN 00be941000-00ffffffff   1046m ----- SmFixed
--16527:2:aspacem    >>>
......
--16527--    -d
--16527--    --leak-check=yes
--16527-- Contents of /proc/version:
--16527--   Linux version 3.4.0-eng-g8b0aff7-00013-g2cb89e3 (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Apr 1 17:30:08 IST 2014
--16527-- Arch and hwcaps: ARM, ARMv7-vfp-neon
--16527-- Page sizes: currently 4096, max supported 4096
--16527-- Valgrind library directory: /system/lib/valgrind
--16527:1:main     ...finished the preamble
--16527:1:main     Initialise the tool part 2 (post_clo_init)
--16527:1:main     Initialise TT/TC
--16527-- TT/TC: VG_(init_tt_tc) (startup of code management)
--16527-- TT/TC: cache: 8 sectors of 27597024 bytes each = 220776192 total
--16527-- TT/TC: table: 524168 total entries, max occupancy 340704 (65%)
--16527:2:transtab   cache: 8 sectors of 27597024 bytes each = 220776192 total
--16527:2:transtab   table: 524168 total entries, max occupancy 340704 (65%)
...
...
--16527-- TT/TC: initialise sector 0
--16527-- Reading syms from /system/lib/valgrind/vgpreload_core-arm-linux.so
--16527--    svma 0x0000000274, avma 0x0004816274
--16527-- Reading syms from /system/lib/libc.so
--16527--    svma 0x000000d1a0, avma 0x00048251a0
--16527--   Considering /system/lib/libc.so ..
--16527--   .. CRC mismatch (computed aedb52cb wanted eadc3e5a)
--16527--    object doesn't have a symbol table
--16527-- Reading syms from /system/lib/libstdc++.so
--16527--    svma 0x0000000828, avma 0x0004873828
--16527--   Considering /system/lib/libstdc++.so ..
--16527--   .. CRC mismatch (computed 7fca0904 wanted e3efd32e)
--16527--    object doesn't have a symbol table
--16527-- Reading syms from /system/lib/libm.so
--16527--    svma 0x0000002940, avma 0x0004878940
--16527--   Considering /system/lib/libm.so ..
--16527--   .. CRC mismatch (computed 5c966341 wanted 751310f2)
--16527--    object doesn't have a symbol table
--16527-- Reading syms from /system/lib/valgrind/vgpreload_memcheck-arm-linux.so
--16527--    svma 0x00000023d4, avma 0x00048933d4
--16527:2:transtab   discard_translations(0x4873919, 1) req by redir_new_DebugInfo(from_addr)
--16527:2:transtab                       FAST, ec = 231
--16527:2:transtab   discard_translations(0x489946c, 1) req by redir_new_DebugInfo(to_addr)
--16527:2:transtab                       FAST, ec = 50
==16527== Adding active redirection:
--16527:1:mallocfr newSuperblock at 0x642AF000 (pszB   65520)  owner VALGRIND/demangle
--16527:1:mallocfr deferred_reclaimSuperblock at 0x642AF000 (pszB   65520)  (prev 0x0) owner VALGRIND/demangle
......

Complete log available at https://docs.google.com/document/d/1hJFGlDeK9Xyujoa6TaOmOdAVNYH4heApyOZY5C3xxqM/edit

Please help.  What does --soname-synonyms=somalloc=NONE do?


On Monday, 26 May 2014, 15:32, Marc Sampé <mar...@gm...> wrote:
 


Keep us updated pls
El 26/05/2014 11:59, "Vignesh" <mv...@ya...> escribió:

Thank you.  My executable was a statically linked one.   
>
>
>Will change it to a dynamic executable and hope to have no issues.
>
>
>-Vignesh
>
>
>
>On Saturday, 24 May 2014, 23:24, Philippe Waroquiers <phi...@sk...> wrote:
> 
>
>
>On Sat, 2014-05-24 at 12:21 +0100, Vignesh wrote:
>
>
>> 
>> ==268== HEAP
 SUMMARY:
>> ==268==     in use at exit: 0 bytes in 0 blocks
>> ==268==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
>This seems to indicate that malloc interception is not working.
>
>Try to run with -v -v -v -d -d -d -trace-redir=yes
>and look in the trace to see what is going wrong.
>
>Note that your application cannot be statically linked,
>otherwise redir of malloc et al does not work.
>(the dynamic linker must be invoked).
>The malloc library itself can be statically linked but
>you need to use --soname-synonyms=somalloc=NONE 
>arg then.
>
>Philippe
>
>
>
>
>
>
>
>------------------------------------------------------------------------------
>The best possible search technologies are now affordable for all companies.
>Download your FREE open source Enterprise Search Engine today!
>Our experts will assist you in its installation for $59/mo, no commitment.
>Test it for FREE on our Cloud platform anytime!
>http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
>_______________________________________________
>Valgrind-users mailing list
>Val...@li...
>https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>

Re: [Valgrind-users] DHAT, MASSIF, External_Fragmentation

[Milian W. <ma...@mi...>]

On Monday 26 May 2014 12:15:32 Rentas Dimitris wrote:
> Hello to the community once more.
> My concern is if I can use DHAT and MASSIF to measure the external
> fragmentation of my application which is using the default Ubuntu 
ptmalloc2
> allocator.
> I have found a several formulas on the paper The Memory Fragmentation
> Problem : Solved?, most of them use the live memory, maximum amount 
of
> memory used by the allocator, maximum amount requested by the 
program.
> How can I interpret the DHAT and MASSIF output to get those values?
> In case you have any other suggestion for another formula please let me
> know.
> 
> I am aware that the most common way is to find the largest free 
contiguous
> block in heap, relative to the total heap amount. But I have not figured
> out how to get this measurement.
> 
> If you have any information or tip it will be a real great help.
> 
> Thank you everyone in advance

Also take a look at mallinfo from malloc.h. It will give you information on the 
fragmentation when you compare .keepcost vs. .uordblks.

Bye

-- 
Milian Wolff
ma...@mi...
http://milianw.de

Re: [Valgrind-users] DHAT, MASSIF, External_Fragmentation

[Philippe W. <phi...@sk...>]

Both dhat and massif are replacing the memory allocator.
So, as the memory fragmentation is very dependent on the 
allocator behaviour (and not only from the application malloc/free
pattern/behaviour), you will not get much additional information
from these tools that what you can certainly get from
ptmalloc2 itself (I guess it has some statistical reporting
and/or support mallinfo or similar).

Philippe


On Mon, 2014-05-26 at 12:15 +0200, Rentas Dimitris wrote:
> Hello to the community once more. 
> My concern is if I can use DHAT and MASSIF to measure the external
> fragmentation of my application which is using the default Ubuntu
> ptmalloc2 allocator. 
> I have found a several formulas on the paper The Memory Fragmentation
> Problem : Solved?, most of them use the live memory, maximum amount of
> memory used by the allocator, maximum amount requested by the
> program. 
> How can I interpret the DHAT and MASSIF output to get those values? 
> In case you have any other suggestion for another formula please let
> me know. 
> 
> 
> I am aware that the most common way is to find the largest free
> contiguous block in heap, relative to the total heap amount. But I
> have not figured out how to get this measurement. 
> 
> 
> If you have any information or tip it will be a real great help.
> 
> 
> Thank you everyone in advance
>  
> ------------------------------------------------------------------------------
> The best possible search technologies are now affordable for all companies.
> Download your FREE open source Enterprise Search Engine today!
> Our experts will assist you in its installation for $59/mo, no commitment.
> Test it for FREE on our Cloud platform anytime!
> http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
> _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users

[Valgrind-users] DHAT, MASSIF, External_Fragmentation

[Rentas D. <dr...@gm...>]

Hello to the community once more.
My concern is if I can use DHAT and MASSIF to measure the external
fragmentation of my application which is using the default Ubuntu ptmalloc2
allocator.
I have found a several formulas on the paper The Memory Fragmentation
Problem : Solved?, most of them use the live memory, maximum amount of
memory used by the allocator, maximum amount requested by the program.
How can I interpret the DHAT and MASSIF output to get those values?
In case you have any other suggestion for another formula please let me
know.

I am aware that the most common way is to find the largest free contiguous
block in heap, relative to the total heap amount. But I have not figured
out how to get this measurement.

If you have any information or tip it will be a real great help.

Thank you everyone in advance

Re: [Valgrind-users] Problem in getting valgrind to run on android

[Marc S. <mar...@gm...>]

Keep us updated pls
El 26/05/2014 11:59, "Vignesh" <mv...@ya...> escribió:

> Thank you.  My executable was a statically linked one.
>
> Will change it to a dynamic executable and hope to have no issues.
>
> -Vignesh
>
>
>   On Saturday, 24 May 2014, 23:24, Philippe Waroquiers <
> phi...@sk...> wrote:
>
>
> On Sat, 2014-05-24 at 12:21 +0100, Vignesh wrote:
>
>
> >
> > ==268== HEAP SUMMARY:
> > ==268==    in use at exit: 0 bytes in 0 blocks
> > ==268==  total heap usage: 0 allocs, 0 frees, 0 bytes allocated
>
> This seems to indicate that malloc interception is not working.
>
> Try to run with -v -v -v -d -d -d -trace-redir=yes
> and look in the trace to see what is going wrong.
>
> Note that your application cannot be statically linked,
> otherwise redir of malloc et al does not work.
> (the dynamic linker must be invoked).
> The malloc library itself can be statically linked but
> you need to use --soname-synonyms=somalloc=NONE
> arg then.
>
> Philippe
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> The best possible search technologies are now affordable for all companies.
> Download your FREE open source Enterprise Search Engine today!
> Our experts will assist you in its installation for $59/mo, no commitment.
> Test it for FREE on our Cloud platform anytime!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>

Re: [Valgrind-users] Problem in getting valgrind to run on android

[Vignesh <mv...@ya...>]

Thank you.  My executable was a statically linked one.   

Will change it to a dynamic executable and hope to have no issues.

-Vignesh


On Saturday, 24 May 2014, 23:24, Philippe Waroquiers <phi...@sk...> wrote:
 


On Sat, 2014-05-24 at 12:21 +0100, Vignesh wrote:


> 
> ==268== HEAP SUMMARY:
> ==268==     in use at exit: 0 bytes in 0 blocks
> ==268==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
This seems to indicate that malloc interception is not working.

Try to run with -v -v -v -d -d -d -trace-redir=yes
and look in the trace to see what is going wrong.

Note that your application cannot be statically linked,
otherwise redir of malloc et al does not work.
(the dynamic linker must be invoked).
The malloc library itself can be statically linked but
you need to use --soname-synonyms=somalloc=NONE 
arg then.

Philippe

Re: [Valgrind-users] Valgrind 3.9 DHAT

[Tom H. <to...@co...>]

On 26/05/14 07:56, Rentas Dimitris wrote:

> Hello everyone. I have a question regarding the dhat tool.
>
> In my Ubuntu machine I have the 3.9 version of valgrind installed.
> However, there is no option for the DHAT tool. Is the tool deprecated,
> or something went wrong during the installation?

What makes you think it is missing? What command are you running?

You realise that, as an experimental tool, it is called exp-dhat right, 
so to run it you need to use:

valgrind --tool=exp-dhat

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/

[Valgrind-users] Valgrind 3.9 DHAT

[Rentas D. <dr...@gm...>]

Hello everyone. I have a question regarding the dhat tool.

In my Ubuntu machine I have the 3.9 version of valgrind installed. However,
there is no option for the DHAT tool. Is the tool deprecated, or something
went wrong during the installation?

Looking forward to hearing from you.

Re: [Valgrind-users] Problem in getting valgrind to run on android

[Philippe W. <phi...@sk...>]

On Sat, 2014-05-24 at 12:21 +0100, Vignesh wrote:

> 
> ==268== HEAP SUMMARY:
> ==268==     in use at exit: 0 bytes in 0 blocks
> ==268==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
This seems to indicate that malloc interception is not working.

Try to run with -v -v -v -d -d -d -trace-redir=yes
and look in the trace to see what is going wrong.

Note that your application cannot be statically linked,
otherwise redir of malloc et al does not work.
(the dynamic linker must be invoked).
The malloc library itself can be statically linked but
you need to use --soname-synonyms=somalloc=NONE 
arg then.

Philippe

[Valgrind-users] Problem in getting valgrind to run on android

[Vignesh <mv...@ya...>]

Hi,

I am having troubles finding memory leaks and array over shoots with valgrind on android.

I have a binary that intentionally leaks few bytes.  When I run the binary in valgrind environment on an android phone (adb shell), I see valgrind reporting no errors.

Please help me understand if I am missing any.  I compiled valgrind that came with android release under external directory (git clone https://android.googlesource.com/platform/external/valgrind)

My program:
--------------
#include <stdio.h>
#include <unistd.h>
#include <stdlib.h>

int main(int argc, char** argv) {
    int i = 0;

    char *leak = (char *) malloc(10);

    char *noleak = (char *)malloc(20);

    free(noleak);
    noleak = NULL;

    return 0;
}

Name of the executable: sample

Output from valgrind:
------------------------

@android:/system/bin # ./valgrind --leak-check=full --tool=memcheck  -v sample
==268== Memcheck, a memory error detector
==268== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==268== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==268== Command: sample
==268== 
--268-- Valgrind options:
--268--    --leak-check=full
--268--    --tool=memcheck
--268--    -v
--268-- Contents of /proc/version:
--268--   Linux version 3.4.42-eng-gcd82698-00002-g6497f5b (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed May 21 17:30:16 IST 2014
--268-- Arch and hwcaps: ARM, ARMv7-vfp-neon
--268-- Page sizes: currently 4096, max supported 4096
--268-- Valgrind library directory: /system/lib/valgrind
--268-- Reading syms from /system/bin/sample
--268--   Considering /system/bin/sample ..
--268--   .. CRC mismatch (computed 918c9dfe wanted cde23cf7)
--268--    object doesn't have a symbol table
--268--    object doesn't have a dynamic symbol table
--268-- Reading syms from /system/lib/valgrind/memcheck-arm-linux
--268--   Considering /system/lib/valgrind/memcheck-arm-linux ..
--268--   .. CRC mismatch (computed 9317450f wanted 4a9e0d91)
--268--    object doesn't have a symbol table
--268--    object doesn't have a dynamic symbol table
--268-- Scheduler: using generic scheduler lock implementation.
--268-- Reading suppressions file: /system/lib/valgrind/default.supp
==268== 
==268== HEAP SUMMARY:
==268==     in use at exit: 0 bytes in 0 blocks
==268==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==268== 
==268== All heap blocks were freed -- no leaks are possible
==268== 
==268== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==268== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Please help.

Regards,
Vignesh

Re: [Valgrind-users] setns syscall with valgrind

[John R. <jr...@Bi...>]

> In our code we use setns system call. [In] valgrind version (3.8.1), it seems like this syscall is not handled. 
> 
> 
> --2726-- WARNING: unhandled syscall: 308
> --2726-- You may be able to write your own handler.
> --2726-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
> --2726-- Nevertheless we consider this a bug.  Please report
> --2726-- it at http://valgrind.org/support/bug_reports.html.


Version 3.9.0 was released about 7 or 8 months ago.  Why not upgrade?

You should tell us which hardware architecture and which operating system.

Because the setns system call:
	int setns(int fd, int nstype);
does not reference memory, then setns is a no-operation as far as memcheck is concerned.
Write an empty subroutine and put its address into the table:
	static SyscallTableEntry syscall_table[] = { ... };
Then submit your patch at the indicated URL.

[Valgrind-users] setns syscall with valgrind

[Himanshu S <mai...@gm...>]

Hello,
I started using valgrind for our code and it is a great tool. In our code
we use setns system call. It seems like valgrind version (3.8.1). It seems
like this syscall is not handled.


--2726-- WARNING: unhandled syscall: 308
--2726-- You may be able to write your own handler.
--2726-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2726-- Nevertheless we consider this a bug.  Please report
--2726-- it at http://valgrind.org/support/bug_reports.html.

I wanted to check if anyone knows about this issue being fixed or if anyone
has a patch that works?

Thanks in advance
-Himanshu

Re: [Valgrind-users] Valgrind doesn't detect leaks on Linux/ARM with uClibc

[Andrejs B. <sin...@gm...>]

On 5/22/14, Andrejs Bogdanovs wrote:
> On 5/22/14, Julian Seward wrote:
>>
>>
>> Does uCLibc implement LD_PRELOAD?  I think that is how Valgrind causes
>> those two objects to be loaded into the process.
>>
>>
>
> tl;dr uclibc must be configured with LD_PRELOAD in order for
> valgrind's memcheck to work. "
>
> Will try to do that.
>
Recompiled uClibc configured with LD_PRELOAD, recompiled example
program and Valgrind and it works now!
Thank you guys!

Re: [Valgrind-users] Valgrind doesn't detect leaks on Linux/ARM with uClibc

[Andrejs B. <sin...@gm...>]

On 5/22/14, Julian Seward wrote:
>
> That soname looks ok, then.  But from the log you posted
> later, it is clear that there is no malloc intercepting happening.
>
> For malloc intercepting to work, the files vgpreload_core-arm-linux.so
> and vgpreload_memcheck-amd64-linux.so need to be loaded into the process.
>
> Comparing your log with a run with a glibc based system, I see this
>
>   Reading syms from [..]/vgpreload_core-amd64-linux.so
>   Reading syms from [..]/vgpreload_memcheck-amd64-linux.so
>
> which is missing in your log.
>
> Does uCLibc implement LD_PRELOAD?  I think that is how Valgrind causes
> those two objects to be loaded into the process.
>
> J
>
That may be a clue!

Actually Valgrind sets LD_PRELOAD env variable to correct string,
pointing to existing /usr/lib/valgrind/vgpreload_core-arm-linux.so and
/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so, but uClibc may have
been configured without LD_PRELOAD.
I've found this in blog entry from NeoSkye:
http://drivingtux.blogspot.com/2013/10/getting-valgrind-memcheck-to-work-with.html

He wrote:
"It turns out that valgrind actually sets the LD_PRELOAD environment
variable early in execution, before loading the executable that is to
be analyzed. This should instruct the runtime link loader to load the
libraries in LD_PRELOAD, which are the vgpreload ones. Unfortunately,
if your uclibc is configured without LD_PRELOAD (like ours was), the
loader will ignore LD_PRELOAD and valgrind won't know that the
vgpreload libraries were never loaded and malloc was not replaced.

tl;dr uclibc must be configured with LD_PRELOAD in order for
valgrind's memcheck to work. "

Will try to do that.