Bug 498614 - callgrind_control equivalent with vgdb ?
Summary: callgrind_control equivalent with vgdb ?
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: callgrind (show other bugs)
Version: 3.24 GIT
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Josef Weidendorfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-13 16:47 UTC by Fred M
Modified: 2025-01-13 19:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Fred M 2025-01-13 16:47:01 UTC 
Hello,

I have difficulty to run callgrind, the real time is blocking the boot.
So I run  it with : --instr-atstart=no  , to start it correctly.

Nevertheless, I can't use "callgrind_control -i on 12345" to enable it because I haven't perl.

Would it have a similar command usable with "vgdb" ?

( I am on a ARM device )

Regards,
Frédéric
Comment 1 Fred M 2025-01-13 16:53:39 UTC 
or maybe an argument valgrind to ask to start after X instruction ?
Comment 2 Fred M 2025-01-13 19:36:16 UTC 
Well, I found "vgdb instrumentation on" in the callgrind_control script