https://bugs.kde.org/show_bug.cgi?id=475634

            Bug ID: 475634
           Summary: valgrind is no starting
    Classification: Developer tools
           Product: valgrind
           Version: 3.22 GIT
          Platform: Other
                OS: Other
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: massif
          Assignee: n...@valgrind.org
          Reporter: dark_foo...@yahoo.fr
  Target Milestone: ---

SUMMARY
I am running the git master version of 03 October 23.

I am launching a heavy software

Ran this : 
valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0'
'--trace-children=yes' '--threshold=0.01' '--main-stacksize=10000000'  my_soft
&

Valgrind is starting with this :
==2807== Massif, a heap profiler
==2807== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==2807== Using Valgrind-3.22.0.GIT and LibVEX; rerun with -h for copyright info

But as I have a backtrace and this warning : 
==2807==  If you believe this happened as a result of a stack                   
==2807==  overflow in your program's main thread (unlikely but                  
==2807==  possible), you can try to increase the size of the
==2807==  main thread stack using the --main-stacksize= flag.
==2807==  The main thread stack size used in this run was 10002432.

I re-do :
valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0'
'--trace-children=yes' '--threshold=0.01' '--main-stacksize=12000000'  my_soft
&

I have no more the starting log: "Massif, a heap profiler" 

and : 
vgdb detailed_snapshot /tmp/massif2023-10-15_00-02-50_0.out
vgdb error: no FIFO found and no pid given

It is as "valgrind is not started at all"

and 
Strangely by removing the "&" at the end of the line 
valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0'
'--trace-children=yes' '--threshold=0.01' '--main-stacksize=12000000'  my_soft
I see the "Massif, a heap profiler" boot log.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ARM chipset

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to