https://bugs.kde.org/show_bug.cgi?id=369456
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #3 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
I ported and tested vgdb on macos some years ago, so the basic of vgdb should
work.
What is not done on macos is the (optional) vgdb (ptrace based on linux)
functionality
that takes a process out of a syscall.
Another difference between vgdb on linux and macos is that vgdb cannot find
the command line by opening "/proc/%d/cmdline", pid);
This means vgdb -l reports e.g.
use --pid=93572 for (could not open process command line)
This is probably the reason for which callgrind_control does not work, as I
guess it expects
something that matches :
if (/^use --pid=(\d+) for \S*?valgrind\s+(.*?)\s*$/) {
So, I suppose that fixing the perl regexp there to also match the (could not
....)
should allow callgrind_control to work
--
You are receiving this mail because:
You are watching all bug changes.
