valgrind-users — General discussion list for Valgrind users

Re: [Valgrind-users] using valgrind to debug uninitialized mem in servern

[Matthias A. <gu...@un...>]

El día jueves, febrero 04, 2021 a las 09:48:23a. m. +0000, Tom Hughes escribió:

> On 04/02/2021 09:26, Matthias Apitz wrote:
> 
> > At the moment we use the following "trick": the librarian runs in
> > parallel to the client on the desktop a second window with a "tail -f ..."
> > on valgrinds log file (STDOUT) and the full screen is recorded with
> > Microsoft teams functionality. So we can use the timestamps in the log
> > to go to the replay of the recording and can see what the user did
> > exactly, which data was entered and which button pressed etc.
> > 
> > Are there other ideas to bring together the valgrind log and the usage
> > of the application?
> 
> You could instrument the request processing logic to log details
> of the request if any errors are detected while processing it, so
> something like:
> 
>   #include "valgrind/valgrind.h"
> 
>   return_type process_request(...)
>   {
>     int errors = VALGRIND_COUNT_ERRORS;
> 
>     // process request as normal
> 
>     if (VALGRIND_COUNT_ERRORS > errors)
>     {
>       VALGRIND_PRINTF("Saw errors processing request %s", request_name);
>     }
>   }
> 
> Obviously you can change it to log whatever details you want.

Thanks, this looks like a good plan!

The above are macros, are there additional shared libs to link with our
process?

> 
> The only issue might be that if the code is multithreaded and can
> process multiple requests in parallel then you won't know which
> thread the errors came from.

No, they're singlethreaded. A master daemon forks for any connecting
client a new server proc.

	matthias

-- 
Matthias Apitz, ✉ gu...@un..., http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

Re: [Valgrind-users] using valgrind to debug uninitialized mem in servern

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

On 04/02/2021 09:26, Matthias Apitz wrote:

> At the moment we use the following "trick": the librarian runs in
> parallel to the client on the desktop a second window with a "tail -f ..."
> on valgrinds log file (STDOUT) and the full screen is recorded with
> Microsoft teams functionality. So we can use the timestamps in the log
> to go to the replay of the recording and can see what the user did
> exactly, which data was entered and which button pressed etc.
> 
> Are there other ideas to bring together the valgrind log and the usage
> of the application?

You could instrument the request processing logic to log details
of the request if any errors are detected while processing it, so
something like:

   #include "valgrind/valgrind.h"

   return_type process_request(...)
   {
     int errors = VALGRIND_COUNT_ERRORS;

     // process request as normal

     if (VALGRIND_COUNT_ERRORS > errors)
     {
       VALGRIND_PRINTF("Saw errors processing request %s", request_name);
     }
   }

Obviously you can change it to log whatever details you want.

The only issue might be that if the code is multithreaded and can
process multiple requests in parallel then you won't know which
thread the errors came from.

Tom

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

[Valgrind-users] using valgrind to debug uninitialized mem in servern

[Matthias A. <gu...@un...>]

Hello,

The following is not fully on-topic because it's more a question related
to how to use valgrind in our case. But maybe others have had similar
questions or a solution...

We have fat application servers, written in C/C++ on top of a DBS
(PostgreSQL). These application servers offer the business logic in a
Library Management System to application clients, written in Java, and
used by the librarian staff of the institutions. Both, server and
client, communicate over a TCP/IP protocol, developed for this purpose
by us: the librarian works with client, the client sends business
oriented commands to the app server, this does its work in the DBS and gives
responses to the client.

We do valgrinding the server and from time to time valgrind detects a
problem, for example usage of not initialized memory access, or jumps
based on this, etc.

Sometimes it is very difficult to find the exact reason for valgrind's
complaint and one has to use a gdb and for this to redo what the server
was executing, or better what the librarian did exactly with the client
that caused the server to execute this particular  piece of code and
with which data input.

At the moment we use the following "trick": the librarian runs in
parallel to the client on the desktop a second window with a "tail -f ..." 
on valgrinds log file (STDOUT) and the full screen is recorded with
Microsoft teams functionality. So we can use the timestamps in the log
to go to the replay of the recording and can see what the user did
exactly, which data was entered and which button pressed etc.

Are there other ideas to bring together the valgrind log and the usage
of the application?

Thanks for reading this.

	matthias
-- 
Matthias Apitz, ✉ gu...@un..., http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

Re: [Valgrind-users] printing the values of arguments for strcpy(3), memmove(3), ...

[Matthias A. <gu...@un...>]

El día martes, enero 26, 2021 a las 02:40:26p. m. -0800, John Reiser escribió:

> > The reason was at the end of debugging that we replaced in some central
> > place of the server a function call (due to vg messages about
> > overlapping args)
> > 
> > 	strncpy(dst, src, n);
> > 
> > by
> > 
> > 	memset(dst, 0, n);
> > 	memmove(dst, src, n);
> > 
> > which is not fully equivalent because strncpy(3) will stop at the first
> > \0 byte in src, while memmove(3) will copy n bytes, regardles if they
> > are valid bytes in src. As this was in some low level function, it
> > generated a mass of the above vg messages.
> [[snip]]
> > Any thoughts about this?
> 
> You may have a much bigger problem than you realize.  Take paper
> and pencil; write TEN TIMES (this is not a joke!):
> 
>      strncpy(dst, src, n) always over-writes exactly n bytes
>      (namely dst[0..(n-1)]), regardless of strlen(src).

I know this. strncpy(dst, src, n) writes strlen(src) bytes to dst and
fills the rest in dst until n with \0 bytes. This is clear but not the point of
the problem. The problem is (was) that strncpy(dst, src, n) only
reads(!) strlen(src) bytes from src, while memmove(dst, src, n) reads n
bytes from src and if n > strlen(src) it reads illegal bytes, raised as
an error by valgrind correctly.

	matthias


-- 
Matthias Apitz, ✉ gu...@un..., http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
¡Con Cuba no te metas!  «»  Don't mess with Cuba!  «»  Leg Dich nicht mit Kuba an!
http://www.cubadebate.cu/noticias/2020/12/25/en-video-con-cuba-no-te-metas/

Re: [Valgrind-users] [valgrind]: mem leaks

[Kunal C. <atk...@gm...>]

++ by using that flag my process is affecting, or there is some thread
optimization flags in valgrind so fruit full logs can be generate

On Wed, Jan 27, 2021 at 11:00 PM Kunal Chauhan <atk...@gm...>
wrote:

> Thanks for hint or approach.
> but My concern was, my valgrind is displaying 1000 error but I want
> valgrind should not stop at error limit .
> as I used --error limit option in valgrind my process some threads does
> not work or process in not well executing.
>
> On Wed, Jan 27, 2021 at 9:42 PM Paul Floyd <pj...@wa...> wrote:
>
>>
>> On 1/27/21 4:31 PM, Kunal Chauhan wrote:
>> > As you said if valgrind is just a same as my process with some extra
>> > messages. But as I facing in valgrind when i used  valgrind option
>> > like --errorlimit=no then my process some threads are not working .
>> >
>> > And if my do not use error limit flag  valgrind saying 1000 error
>> > reached and it will not display more errors , how can i come out of
>> > this situation.
>> >
>>
>> I was only referring to segmentation faults.
>>
>>
>> If there are other errors you will have to fix them. Just start at with
>> the first one and continue.
>>
>>
>> Regards
>>
>> Paul
>>
>>
>>
>
> --
> *Thanks with Regards!*
>
> *Kunal Chauhan*
> *Mob:09813614826*
> *Mob:08860397903*
>
> *E-mail:atk...@gm... <E-mail%3Aa...@gm...>*
>
>

-- 
*Thanks with Regards!*

*Kunal Chauhan*
*Mob:09813614826*
*Mob:08860397903*

*E-mail:atk...@gm... <E-mail%3Aa...@gm...>*

Re: [Valgrind-users] [valgrind]: mem leaks

[Kunal C. <atk...@gm...>]

Thanks for hint or approach.
but My concern was, my valgrind is displaying 1000 error but I want
valgrind should not stop at error limit .
as I used --error limit option in valgrind my process some threads does not
work or process in not well executing.

On Wed, Jan 27, 2021 at 9:42 PM Paul Floyd <pj...@wa...> wrote:

>
> On 1/27/21 4:31 PM, Kunal Chauhan wrote:
> > As you said if valgrind is just a same as my process with some extra
> > messages. But as I facing in valgrind when i used  valgrind option
> > like --errorlimit=no then my process some threads are not working .
> >
> > And if my do not use error limit flag  valgrind saying 1000 error
> > reached and it will not display more errors , how can i come out of
> > this situation.
> >
>
> I was only referring to segmentation faults.
>
>
> If there are other errors you will have to fix them. Just start at with
> the first one and continue.
>
>
> Regards
>
> Paul
>
>
>

-- 
*Thanks with Regards!*

*Kunal Chauhan*
*Mob:09813614826*
*Mob:08860397903*

*E-mail:atk...@gm... <E-mail%3Aa...@gm...>*

Re: [Valgrind-users] [valgrind]: mem leaks

[Paul F. <pj...@wa...>]

> On 25 Jan 2021, at 11:49, Kunal Chauhan <atk...@gm...> wrote:
> 
> Thanks for clarifications
> ++ if the binary is crashed or may be not crashed when it runs with valgrind, but in both case valgrind is able to give the report. ?


Hi

If your application causes a segmentation fault, the OS will send it a SIGSEGV signal. When it is running inside Valgrind, Valgrind will see whether or not your application has a signal handler. If not it will print a message describing the fault and also instructions as to what you should do in the unlikely event that the cause is a stack overflow in your program’s main thread.

In short, Valgrind will do the same as you application would do running outsizde of Valgrind, just with a lot more messages.

A+
Paul

Re: [Valgrind-users] printing the values of arguments for strcpy(3), memmove(3), ...

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

> The reason was at the end of debugging that we replaced in some central
> place of the server a function call (due to vg messages about
> overlapping args)
> 
> 	strncpy(dst, src, n);
> 
> by
> 
> 	memset(dst, 0, n);
> 	memmove(dst, src, n);
> 
> which is not fully equivalent because strncpy(3) will stop at the first
> \0 byte in src, while memmove(3) will copy n bytes, regardles if they
> are valid bytes in src. As this was in some low level function, it
> generated a mass of the above vg messages.
[[snip]]
> Any thoughts about this?

You may have a much bigger problem than you realize.  Take paper
and pencil; write TEN TIMES (this is not a joke!):

      strncpy(dst, src, n) always over-writes exactly n bytes
      (namely dst[0..(n-1)]), regardless of strlen(src).

A large fraction of lexical calls to strncpy are incorrect;
the code just happens to work "by accident".

First, if there is any overlap between the intervals dst[0..(n-1)]
and src[0..(n-1)] then the result is undefined.  The implementation
of strncpy is allowed to read and write bytes in ANY order: lowest
index first, highest index first, single byte at a time, multiple
bytes at a time, interleaving Read and Write in any order (including
writing into the same byte multiple times, or writing an incorrect
value but correcting it later), etc.  Also, all str* functions are
allowed to fetch beyond src[1+ strlen(src)] as long as there can be
no SIGSEGV; and to store into dst[n] and beyond, as long as there is
no change there.  So any byte that is within the memory words or
cache lines that cover src[] or dst[] is fair game to be included
in a memory operation of strncpy.

Second, if (strlen(src) < n) then strncpy zeroes the remaining bytes
through dst[n-1].

Third, if (strlen(src) >= n) then dst is not NUL terminated.

Recommendation: search all the source code of all the projects
of your entire team/department/company for strncpy, and fix the bugs.

-- 

Re: [Valgrind-users] printing the values of arguments for strcpy(3), memmove(3), ...

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

On 26/01/2021 09:32, Matthias Apitz wrote:

> So far so good. What would have helped me is that vg could print in its
> replacement functions for memmove(3) ... (vg_replace_strmem.c:1270)
> the provided pointers and other args, and as well part of the src
> buffer. For sure vg knows exactly these values to watch the illegal
> memory access.

If the memory is uninitialised then printing it's contents
shouldn't really be useful as they will have no meaning...

Presumably it was partially initialised in this case but it
sounds like quite an edge case and it's easy enough to add
some custom debugging to your code when it does help in cases
like this. I'm not clear if you just printed everything but
you can conditionalise it to only print the failing case:

   if ( VALGRIND_CHECK_MEM_IS_DEFINED( src, n ) )
   {
     fprintf( stderr, "ERROR: %.*s\n", n, src );
   }

if you want to get really clever you can limit it to printing
the valid part:

   const char *fail = VALGRIND_CHECK_MEM_IS_DEFINED( src, n );

   if ( fail )
   {
     fprintf( stderr, "ERROR: %.*s\n", fail - src, src );
   }

Tom

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

[Valgrind-users] printing the values of arguments for strcpy(3), memmove(3), ...

[Matthias A. <gu...@un...>]

Hello,

This is with valgrind 3.14.0 compiled and used on SuSE Linux 12 and 15 x86_64.

I have had a hart time to nail down the reason for a lot(!) of such vg
messages:

==1272== Invalid read of size 8
==1272==    at 0x4C355BF: memmove (vg_replace_strmem.c:1270)
==1272==    by 0x64A50D7: zzstrncpy (zzstdc.C:143)
==1272==    by 0x67366DE: SqlCharToChar (ec_general.ec:165)
==1272==    by 0x675ED84: Para2Host (acq_update.h:59)
==1272==    by 0x675FCE7: SQLExistUpdateEntry (ec_acq_update.ec:200)
...
==1272==  Address 0x17d80148 is 24 bytes after a block of size 16 in arena "client"

The reason was at the end of debugging that we replaced in some central
place of the server a function call (due to vg messages about
overlapping args)

	strncpy(dst, src, n);

by

	memset(dst, 0, n);
	memmove(dst, src, n);

which is not fully equivalent because strncpy(3) will stop at the first
\0 byte in src, while memmove(3) will copy n bytes, regardles if they
are valid bytes in src. As this was in some low level function, it
generated a mass of the above vg messages.

To debug it, I ended up printing in hex the pointer src, the value of n
and the first n bytes of src which finally gave me a clue what was wrong:
the number n was some kind of a fixed maximal length for dst and regardless of
the provided bytes in src. Fixed by:

	memset(dst, 0, n);
	n = strlen(src);
	memmove(dst, src, n);

So far so good. What would have helped me is that vg could print in its
replacement functions for memmove(3) ... (vg_replace_strmem.c:1270)
the provided pointers and other args, and as well part of the src
buffer. For sure vg knows exactly these values to watch the illegal
memory access.

Any thoughts about this?

	matthias

-- 
Matthias Apitz, ✉ gu...@un..., http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
¡Con Cuba no te metas!  «»  Don't mess with Cuba!  «»  Leg Dich nicht mit Kuba an!
http://www.cubadebate.cu/noticias/2020/12/25/en-video-con-cuba-no-te-metas/

Re: [Valgrind-users] [valgrind]: mem leaks

[Kunal C. <atk...@gm...>]

Thanks for clarifications
++ if the binary is crashed or may be not crashed when it runs with
valgrind, but in both case valgrind is able to give the report. ?

On Mon, Jan 25, 2021 at 1:28 PM Paul Floyd <pj...@wa...> wrote:

>
>
> > On 24 Jan 2021, at 18:29, Kunal Chauhan <atk...@gm...>
> wrote:
> >
> > Hi paul,
> >
> > thanks for info,
> > 1.Like  in trailing mail you said process under completion  what do you
> mean exactly,
> > 2. Also for running a process under valgrind my binary should be strip
> or unstrip.?
> >
> > 3. Memcheck tool where it fits in context of valgrind .
>
>
> (Replying to the list)
>
> 1. A command like ‘pwd’. You run the command, it prints the working
> directory and then it exits. In this example when the pwd process
> completes, Valgrind can detect leaks.
> 2. Unstripped binaries with debug information are the best.
> 3. Valgrind includes several tools, memcheck being the best known of them,
> for detecting memory errors. There are also tools for profiling and thread
> hazard detection.
>
> A+
> Paul
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>


-- 
*Thanks with Regards!*

*Kunal Chauhan*
*Mob:09813614826*
*Mob:08860397903*

*E-mail:atk...@gm... <E-mail%3Aa...@gm...>*

Re: [Valgrind-users] [valgrind]: mem leaks

[Paul F. <pj...@wa...>]

> On 24 Jan 2021, at 18:29, Kunal Chauhan <atk...@gm...> wrote:
> 
> Hi paul,
> 
> thanks for info,
> 1.Like  in trailing mail you said process under completion  what do you mean exactly, 
> 2. Also for running a process under valgrind my binary should be strip or unstrip.?
> 
> 3. Memcheck tool where it fits in context of valgrind .


(Replying to the list)

1. A command like ‘pwd’. You run the command, it prints the working directory and then it exits. In this example when the pwd process completes, Valgrind can detect leaks.
2. Unstripped binaries with debug information are the best.
3. Valgrind includes several tools, memcheck being the best known of them, for detecting memory errors. There are also tools for profiling and thread hazard detection.

A+
Paul

Re: [Valgrind-users] [valgrind]: mem leaks

[Paul F. <pj...@wa...>]

On 1/22/21 9:31 PM, Kunal Chauhan wrote:
> Hi Team,
>
> As on my linux  board ,one of process showing some run time memory 
> increase as seen by pmap command.
>
> So how valgrind can be useful to search such mem leaks in big code.
>
> Or is there is way to attached valgrind and see where and which 
> instruction actually causing issue


Hi

You can't 'attach' Valgrind to a running process.

What you need to do is to run the process under Valgrind. If the process 
normally runs to completion, you can just run it under Valgrind (by 
default, the memcheck tool will be used, add --leak-check=full and 
possibly --show-reachable=yes).

If the process is running aas a daemon, then your best bet is to run it 
under Valgrind and then attach gdb to it and use monitor commands to 
check for leaks. That is documented on the Valgrind web page, here 
https://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver-commandhandling 
.


A+

Paul

[Valgrind-users] [valgrind]: mem leaks

[Kunal C. <atk...@gm...>]

Hi Team,

As on my linux  board ,one of process showing some run time memory increase
as seen by pmap command.

So how valgrind can be useful to search such mem leaks in big code.

Or is there is way to attached valgrind and see where and which instruction
actually causing issue

[Valgrind-users] [valgrind]: mem leak find

[Kunal C. <atk...@gm...>]

Hi Team,


As I am facing some issue , like it seems one my process on linux board is
increasing its size as seen by pmap commands.

So how valgrind can be useful to see this type of memleaks , and what
approach to follow up.

Re: [Valgrind-users] Please give me advises: How to use the snapshot parameter used in VALGRIND's massif in external applications like Python or ROS/ROS2

[Paul F. <pj...@wa...>]

On 19/01/2021 17:52, Koki Nagahama wrote:
> Hi VALGRIND developers and users,
> I'm planning to modify a part of your product, VALGRIND,to integrate 
> it with a middleware for robots called ROS.
>
> In order to do this, I'm considering two ways to implement the massif 
> component of VALGRIND: (1) to implement it in C and call it in another 
> program as a Python library, and (2) to convert it into a ROS/ROS2 
> component (nodes) in C++.
>
> The reason for these implementations plan is that I want to retrieve 
> the values of heap_szB and stack_szB defined in the Snapshot structure 
> in ms_main.c of massif via VALGRIND and use them in a timely manner in 
> an external Python-based program.
> As far as I read the raw source code, the way to get the data is to 
> specify the last struct element of Snapshot* snapshot and extract it 
> (if I'm wrong, please let me know).However, I'm struggling with the 
> implementation of the part that passes to the external application.
>
> Please advise me on the implementation, including which method is more 
> feasible.

Hi

This doesn't seem feasible to me.

Massif (and all of the Valgrind tools) does not link with any library. 
This makes life much simpler because generally the guest application 
links with at least libc. If both guest and host link with the same libs 
then that would cause conflicts.

I think that the best way to do something like this is to use a pipe to 
communicate with an external application, similar to the way that tools 
use pipes for communication between gdb and the embedded gdbserver.


A+

Paul

[Valgrind-users] Please give me advises: How to use the snapshot parameter used in VALGRIND's massif in external applications like Python or ROS/ROS2

[Koki N. <her...@gm...>]

Hi VALGRIND developers and users,
I'm planning to modify a part of your product, VALGRIND,to integrate it
with a middleware for robots called ROS.

In order to do this, I'm considering two ways to implement the massif
component of VALGRIND: (1) to implement it in C and call it in another
program as a Python library, and (2) to convert it into a ROS/ROS2
component (nodes) in C++.

The reason for these implementations plan is that I want to retrieve the
values of heap_szB and stack_szB defined in the Snapshot structure in
ms_main.c of massif via VALGRIND and use them in a timely manner in an
external Python-based program.
As far as I read the raw source code, the way to get the data is to specify
the last struct element of Snapshot* snapshot and extract it (if I'm wrong,
please let me know).However, I'm struggling with the implementation of the
part that passes to the external application.

Please advise me on the implementation, including which method is more
feasible.
As for (1), I tried to build the source code to see if I could include
Python.h correctly, and it failed, so I'll keep a log of this.

========
<< Environment >>
$ uname -a
Linux [HOSTNAME] 5.4.0-1026-raspi #29-Ubuntu SMP PREEMPT Mon Dec 14
17:01:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

$ cat /etc/lsb-release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"

<< What I did during the build and the log >>
I made the following changes to the DEFAULTS_INCLEDES variable in the
massif/Makefile.

DEFAULT_INCLUDES = -I. -I$(top_builddir) -I/usr/include/python3.8


I also inserted the following two lines in the first line of
massif/ms_main.c. The following two lines are inserted in the first line of
massif/ms_main.c. No functions using PyObject* are implemented in the file.

#define PY_SSIZE_T_CLEAN
#include <Python.h>.

When I ran make and make install, I got the following error message.

Making all in massif
make[2]: Entering directory '/home/[username]/[work
directory]/valgrind-3.16.1/massif'
Making all in .
make[3]: Entering directory '/home/[username]/[work
directory]/valgrind-3.16.1/massif'
gcc -DHAVE_CONFIG_H -I. -I... -I/usr/include/python3.8 -I.. -I.. /include
-I.. /include -I. /VEX/pub -I. /VEX/pub -DVGA_arm64=1 -DVGO_linux=1
-DVGP_arm64_linux=1 -DVGPV_arm64_linux_vanilla=1 -O2 -g -Wall
-Wmissing-prototypes -Wshadow -Wpointer- arith -Wstrict-prototypes
-Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings
-Wempty-body -Wformat -Wformat-signedness Wformat-security
-Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op
-Wimplicit-fallthrough=2 -Wold-style-declaration -finline- functions
-fno-stack-protector -fno-strict-aliasing -fno-builtin -MT
massif_arm64_linux-ms_main.o -MD -MP -MF .deps/massif_arm64_linux-ms_ Tpo
-c -o massif_arm64_linux-ms_main.o `test -f 'ms_main.c' || echo '.
/'`ms_main.c
In file included from /usr/include/aarch64-linux-gnu/sys/stat.h:101,
                 From /usr/include/python3.8/pyport.h:245,
                 from /usr/include/python3.8/Python.h:63,
                 from ms_main.c:6:
... /include/vki/vki-arm64-linux.h:316:25: error: expected ':', ',', '. ;',
'}' or '__attribute__' before '. token
  316 | long st_atime;
      | ^~~~~~~~
make[3]: *** [Makefile:1087: massif_arm64_linux-ms_main.o] Error 1
make[3]: Leaving directory '/home/[username]/[my work
directory]/valgrind-3.16.1/massif'
make[2]: *** [Makefile:1121: all-recursive] Error 1
make[2]: Leaving directory '/home/[username]/[my work
directory]/valgrind-3.16.1/massif'
make[1]: *** [Makefile:849: all-recursive] Error 1
make[1]: Leaving directory '/home/[username]/[my work
directory]/valgrind-3.16.1'
Make: *** [Makefile:718: all] Error 2

Best regards,
Koki

Re: [Valgrind-users] I need your help because Building VALGRIND is Failing on Ubuntu 20.xx

[Koki N. <her...@gm...>]

Dear Geoff Alexander and Eliot Moss,

Thank you for checking the mailing list and answering my questions.

I added the "--without-mpicc" option to the configure process, and the
build succeeded!
I was not aware that this had been reported in the past.
I didn't check the MPI downgrade, but I'll try it when I can and add it to
this mailing list.

Thanks,
Koki

Re: [Valgrind-users] I need your help because Building VALGRIND is Failing on Ubuntu 20.xx

[Eliot M. <mo...@cs...>]

On 1/14/2021 9:35 AM, Geoff Alexander wrote:
> I wonder if this is related to Valgrind bug 439542 Cannot compile valgrind on Ubuntu 20.04 docker 
> due to failed compilation libmpiwrap.c (https://bugs.kde.org/show_bug.cgi?id=420518).
> 
> Geoff Alexander, Ph.D.
> Software Engineer, Corporate Tools Development
> IBM Corporation
> Charlotte, NC

It seems to be exactly the same issue.

EM

> Koki Nagahama <her...@gm...> wrote on 01/14/2021 02:59:18 AM:
> 
>  > From: Koki Nagahama <her...@gm...>
>  > To: val...@li...
>  > Date: 01/14/2021 03:00 AM
>  > Subject: [EXTERNAL] [Valgrind-users] I need your help because
>  > Building VALGRIND is Failing on Ubuntu 20.xx
>  >
>  > Hi VALGRIND developers, I'm planning to modify a part of your...
>  >
>  > This Message Is From an External Sender
>  >
>  > This message came from outside your organization.
>  >
>  > Hi VALGRIND developers,
>  >
>  > I'm planning to modify a part of your product, VALGRIND,to integrate
>  > it with a middleware for robots called ROS.However, I'm having
>  > trouble building from the Valgrind source code on Ubuntu 20.xx.
>  >
>  > The hardware is a Raspberry Pi 4B+ (aarch64) and the OS is Ubuntu
>  > Mate 20.04 (focal) 64-bit version,so I think ARMv8 is supported, but
>  > I can't seem to get it to work.The source code is from 3.16.1, which
>  > came out this year.
>  >
>  > From reading the errors and warnings, maybe there is an obvious
>  > reason in the source code,but maybe there are other build stoppers
>  > after the one I failed to build,so can you please help me to
>  > investigate the cause and help me to build successfully?
>  >
>  > By the way, Ubuntu 18.04 LTS succeeded in building as usual. It may
>  > be that the package required for make is not included in Ubuntu
>  > 20.xx or is different, but I have no idea.
>  >
>  > I've uploaded the build log of my environment to Google Drive, and
>  > the URL is listed below.Some of the logs are omitted because I ran
>  > the command one more time after one failed build,but I hope it helps
>  > you understand the situation.
>  >
>  > Build log:https://drive.google.com/file/d/1-pxnXa-
>  > GgEYak8k_ITpj504LlBMYbR9H/view?usp=sharing
>  >
>  > Best Regards,
>  > Koki_______________________________________________
>  > Valgrind-users mailing list
>  > Val...@li...
>  > INVALID URI REMOVED
>  > u=https-3A__lists.sourceforge.net_lists_listinfo_valgrind-2Dusers&d=DwICAg&c=jf_iaSHvJObTbx-
>  > siA1ZOg&r=KJ6EIWC2rKHl4x6BfwQuSA&m=KVpnlHdoQ-
>  > kGIfGrpIAYViKHIKfID3QJSLNoDAds8T0&s=PozwhcjX-
>  > _fdLcjkvHCWdXX8fBvwKTYXFJDMpjuDjyQ&e=
> 
> 
> 
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
> 

Re: [Valgrind-users] I need your help because Building VALGRIND is Failing on Ubuntu 20.xx

[Geoff A. <gd...@us...>]

Oops, I meant related to Bug 420518 -- the link I gave is correct.

Geoff Alexander, Ph.D.
Software Engineer, Corporate Tools Development
IBM Corporation
Charlotte, NC


"Geoff Alexander" <gd...@us...> wrote on 01/14/2021 09:35:50 AM:

> From: "Geoff Alexander" <gd...@us...>
> To: Koki Nagahama <her...@gm...>
> Cc: val...@li...
> Date: 01/14/2021 09:36 AM
> Subject: [EXTERNAL] Re: [Valgrind-users] I need your help because
> Building VALGRIND is Failing on Ubuntu 20.xx
>
> I wonder if this is related to Valgrind bug 439542 Cannot compile
> valgrind on Ubuntu 20.04 docker due to failed compilation libmpiwrap.c (
> https://bugs.kde.org/show_bug.cgi?id=420518).
>
> Geoff Alexander, Ph.D.
> Software Engineer, Corporate Tools Development
> IBM Corporation
> Charlotte, NC
>
>

Re: [Valgrind-users] I need your help because Building VALGRIND is Failing on Ubuntu 20.xx

[Geoff A. <gd...@us...>]

I wonder if this is related to Valgrind bug 439542 Cannot compile valgrind
on Ubuntu 20.04 docker due to failed compilation libmpiwrap.c (
https://bugs.kde.org/show_bug.cgi?id=420518).

Geoff Alexander, Ph.D.
Software Engineer, Corporate Tools Development
IBM Corporation
Charlotte, NC


Koki Nagahama <her...@gm...> wrote on 01/14/2021 02:59:18 AM:

> From: Koki Nagahama <her...@gm...>
> To: val...@li...
> Date: 01/14/2021 03:00 AM
> Subject: [EXTERNAL] [Valgrind-users] I need your help because
> Building VALGRIND is Failing on Ubuntu 20.xx
>
> Hi VALGRIND developers, I'm planning to modify a part of your...
>
> This Message Is From an External Sender
>
> This message came from outside your organization.
>
> Hi VALGRIND developers,
>
> I'm planning to modify a part of your product, VALGRIND,to integrate
> it with a middleware for robots called ROS.However, I'm having
> trouble building from the Valgrind source code on Ubuntu 20.xx.
>
> The hardware is a Raspberry Pi 4B+ (aarch64) and the OS is Ubuntu
> Mate 20.04 (focal) 64-bit version,so I think ARMv8 is supported, but
> I can't seem to get it to work.The source code is from 3.16.1, which
> came out this year.
>
> From reading the errors and warnings, maybe there is an obvious
> reason in the source code,but maybe there are other build stoppers
> after the one I failed to build,so can you please help me to
> investigate the cause and help me to build successfully?
>
> By the way, Ubuntu 18.04 LTS succeeded in building as usual. It may
> be that the package required for make is not included in Ubuntu
> 20.xx or is different, but I have no idea.
>
> I've uploaded the build log of my environment to Google Drive, and
> the URL is listed below.Some of the logs are omitted because I ran
> the command one more time after one failed build,but I hope it helps
> you understand the situation.
>
> Build log:https://drive.google.com/file/d/1-pxnXa-
> GgEYak8k_ITpj504LlBMYbR9H/view?usp=sharing
>
> Best Regards,
> Koki_______________________________________________
> Valgrind-users mailing list
> Val...@li...
> INVALID URI REMOVED
>
u=https-3A__lists.sourceforge.net_lists_listinfo_valgrind-2Dusers&d=DwICAg&c=jf_iaSHvJObTbx-

> siA1ZOg&r=KJ6EIWC2rKHl4x6BfwQuSA&m=KVpnlHdoQ-
> kGIfGrpIAYViKHIKfID3QJSLNoDAds8T0&s=PozwhcjX-
> _fdLcjkvHCWdXX8fBvwKTYXFJDMpjuDjyQ&e=

Re: [Valgrind-users] I need your help because Building VALGRIND is Failing on Ubuntu 20.xx

[Eliot M. <mo...@cs...>]

On 1/14/2021 2:59 AM, Koki Nagahama wrote:
> Hi VALGRIND developers,
> 
> I'm planning to modify a part of your product, VALGRIND,to integrate it with a middleware for robots 
> called ROS.However, I'm having trouble building from the Valgrind source code on Ubuntu 20.xx.
> 
> The hardware is a Raspberry Pi 4B+ (aarch64) and the OS is Ubuntu Mate 20.04 (focal) 64-bit 
> version,so I think ARMv8 is supported, but I can't seem to get it to work.The source code is from 
> 3.16.1, which came out this year.
> 
>  From reading the errors and warnings, maybe there is an obvious reason in the source code,but maybe 
> there are other build stoppers after the one I failed to build,so can you please help me to 
> investigate the cause and help me to build successfully?
> 
> By the way, Ubuntu 18.04 LTS succeeded in building as usual. It may be that the package required for 
> make is not included in Ubuntu 20.xx or is different, but I have no idea.
> 
> I've uploaded the build log of my environment to Google Drive, and the URL is listed below.Some of 
> the logs are omitted because I ran the command one more time after one failed build,but I hope it 
> helps you understand the situation.
> 
> Build log:https://drive.google.com/file/d/1-pxnXa-GgEYak8k_ITpj504LlBMYbR9H/view?usp=sharing

It is failing in the stage where it is building MPI support.  Your setup seems to have mpi installed 
(mpicc and mpi.h are found), but apparently not a version of mpi.h that works with valgrind.  You 
might try configuring --without-mpicc or else revert the MPI version to 2.something instead of 
3.something.  (The latter is a little bit of a guess, but because configure --help mentions MPI2.)

HTH - Eliot Moss

[Valgrind-users] I need your help because Building VALGRIND is Failing on Ubuntu 20.xx

[Koki N. <her...@gm...>]

Hi VALGRIND developers,

I'm planning to modify a part of your product, VALGRIND,to integrate it
with a middleware for robots called ROS.However, I'm having trouble
building from the Valgrind source code on Ubuntu 20.xx.

The hardware is a Raspberry Pi 4B+ (aarch64) and the OS is Ubuntu Mate
20.04 (focal) 64-bit version,so I think ARMv8 is supported, but I can't
seem to get it to work.The source code is from 3.16.1, which came out this
year.

>From reading the errors and warnings, maybe there is an obvious reason in
the source code,but maybe there are other build stoppers after the one I
failed to build,so can you please help me to investigate the cause and help
me to build successfully?

By the way, Ubuntu 18.04 LTS succeeded in building as usual. It may be that
the package required for make is not included in Ubuntu 20.xx or is
different, but I have no idea.

I've uploaded the build log of my environment to Google Drive, and the URL
is listed below.Some of the logs are omitted because I ran the command one
more time after one failed build,but I hope it helps you understand the
situation.

Build log:
https://drive.google.com/file/d/1-pxnXa-GgEYak8k_ITpj504LlBMYbR9H/view?usp=sharing

Best Regards,
Koki

Re: [Valgrind-users] [Need Help] Valgrind on Cavium-Octeon-3

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

mihir amrelia wrote:
>> file /var/tmp/cavium/bin/valgrind
>> /var/tmp/cavium/bin/valgrind: ELF 64-bit MSB executable, MIPS, MIPS64 rel2 version 1 (SYSV), dynamically linked, interpreter /lib64-f, for GNU/Linux 2.6.32, not stripped
>>
>> How to fix this?

Tom Hughes via Valgrind-users wrote:
> No idea - that will be down to your cross build toolchain.


Diagnose by something like:
     strace -f -o strace.out -e trace=execve -v -s 400 gcc hello.c
then search for "lib64-f" in strace.out.

For a native compile tool chain the relevant piece in strace.out is something like:
     execve("/usr/bin/ld", ["/usr/bin/ld", ...  "-dynamic-linker", "/lib64/ld-linux-x86-64.so.2", ...
which would be changed by something like
     gcc -Wl,-dynamic-linker,path_to_eventual_dynamic_linker ...

Re: [Valgrind-users] [Need Help] Valgrind on Cavium-Octeon-3

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

No idea - that will be down to your cross build toolchain.

Tom

On 10/01/2021 18:21, mihir amrelia wrote:
> Tom,
> 
> Thanks a lot for your response.
> Yes, it doesn't look like the one I should be expecting..
> 
> file /var/tmp/cavium/bin/valgrind
> /var/tmp/cavium/bin/valgrind: ELF 64-bit MSB executable, MIPS, MIPS64 
> rel2 version 1 (SYSV), dynamically linked, interpreter /lib64-f, for 
> GNU/Linux 2.6.32, not stripped
> 
> How to fix this?
> 
> -Mihir
> On Thursday, 7 January, 2021, 04:36:45 pm IST, Tom Hughes 
> <to...@co...> wrote:
> 
> 
> On 07/01/2021 10:54, mihir amrelia via Valgrind-users wrote:
> 
> 
>  > I am trying to get valgrind running on cavium octeon 3 processor.
>  >
>  >
>  > Couldn't find any specific build configs for this other than some hints
>  > on the valgrind wiki.
>  > *
>  > *
>  > *
>  > The steps executed to build valgrind for cavium were (on x86_64 host):
>  > *export CC=/opt/cavium-64bit/tools-3535/bin/mips64-octeon-linux-gnu-gcc
>  > export CXX=/opt/cavium-64bit/tools-3535/bin/mips64-octeon-linux-gnu-g++
>  > export PATH=$PATH:/opt/cavium-64bit/tools-3535/bin/
>  > ./configure --host=mips64-linux-gnu --target=mips64-octeon-linux
>  > --prefix=/home/mihira/workspace/mylab/valgrind/cavium
>  > --exec-prefix=/var/tmp/cavium --disable-tls
>  > make && make install
>  >
>  > *While trying to run it on target (copied the elfs to /var/tmp/cavium/
>  > dir on the target):*
>  > export VALGRIND_LIB=/var/tmp/cavium/lib/valgrind/
>  > export PATH=$PATH:/var/tmp/cavium/bin/
>  > valgrind -h
>  > -bash: /var/tmp/cavium/bin/valgrind: No such file or directory
>  >
>  >
>  > What's that blunder I am doing?
> 
> 
> At a guess the ELF interpreter specified in the compiled
> valgrind launcher doesn't exist - that can lead to that
> confusing error when running a executable that exists.
> 
> Try "file /var/tmp/cavium/bin/valgrind" and see what it says
> about it - part of the result should be something like this:
> 
>    interpreter /lib64/ld-linux-x86-64.so.2
> 
> which will tell what interpreter it is using.
> 
> Tom
> 
> -- 
> Tom Hughes (to...@co... <mailto:to...@co...>)
> http://compton.nu/ <http://compton.nu/>
> 


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