[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 369456] callgrind_control failed to find an active callgrind run.
From:       Philippe Waroquiers via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2016-09-30 19:12:37
Message-ID: bug-369456-17878-tBXeBBBWE2 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

Philippe Waroquiers <philippe.waroquiers@skynet.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rhyskidd@gmail.com

--- Comment #5 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
(In reply to Alex from comment #4)
> Fixing regex can help to find PID. Something like that (I'm not familiar
> with perl/regex):
> $ vgdb -l | perl -lpe'/^use --pid=(\d+) for [\S\s]+$/; print $1;'
> 30750
> use --pid=30750 for (could not open process command line)
> 
> But callgrind_control also check  that running tool is callgrind.
> There is no such info in the string returning from vgdb -l.
Yes, a proper fix implies to have a way to find the command line (or at least
the
launched executable) on MacOS.
No idea how to do that (and moreover I have no access to a MacOS system).
Maybe Rhys has an idea ?

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]