https://bugs.kde.org/show_bug.cgi?id=369456
--- Comment #6 from Alex ---
May be I can help?
MacOS has proc_pidinfo (from sys/proc_info.h or libproc.h) for obtaining info
about running app.
Probably ps, top and others use it.
Or popen something like "ps -p -o command" and parse.
The second varian
https://bugs.kde.org/show_bug.cgi?id=369456
Philippe Waroquiers changed:
What|Removed |Added
CC||rhysk...@gmail.com
--- Comment #5 from Ph
https://bugs.kde.org/show_bug.cgi?id=369456
--- Comment #4 from Alex ---
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)
Bu
https://bugs.kde.org/show_bug.cgi?id=369456
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet.
https://bugs.kde.org/show_bug.cgi?id=369456
--- Comment #2 from Alex ---
$ vgdb -l
use --pid=93572 for (could not open process command line)
93572 is the right PID of running valgrind.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369456
--- Comment #1 from Josef Weidendorfer ---
callgrind_control uses "vgdb" starting from Valgrind 3.11 to get a list of
running valgrind instances.
Perhaps this is not working on OSX.
What is the output of "vgdb -l" with callgrind running?
--
You are re
