Launch profiler from macOS terminal with sudo

[ianbUK]

launching the profiler from the terminal in macOS as sudo, gets past the '(null) cannot' error, but the profiler just sits there with the 'connecting' dialog shown.

What do I need to do, to get profiling working on a Ventura macOS based M1 MacBook Air, with a .Net Framework 4.8 application?

[ianbUK]

The log file contains the following, does it help diagnose the problem?

Strategy 'desktop' failed: com.github.markusbernhardt.proxy.util.ProxyException: com.github.markusbernhardt.proxy.util.PListParser$XmlParseException: Failed to parse: dict

[Vladimir Kondratyev]

1) Which exact profiler version are you using?

2) For what purpose are you lauching it with "sudo"?

3) Please send to [email protected] exact command you using to launch the profiler; full profiler log file; screnshot of profiler UI

Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"

[Ilya Kalikin]

Hi. Instead of running profiler with sudo to get past Terminal error, you can enable profiling manually by setting few environment variables, please see this help topic.

The reason you can't connect to the application is that you try to profile an unsupported .NET runtime version. On macOS profiling of .NET Framework is not supported. Do you see your .NET Framework application in this application list? Can you please provide a link to the .NET Framework 4.8 runtime you use for macOS?

[Adans23]

When running the YourKit profiler from a terminal with sudo, it is possible that the profiler cannot connect to the application being profiled due to permission issues. You can try: make sure the profiler and the app being profiled are running with the same permissions, make sure the profiler and the app being profiled are running in the same user context, make sure the profiled app is configured to allow profiling, try running the profiler without sudo

[loren56]

To get profiling working on macOS Ventura with .NET Framework 4.8 on an M1 Mac, ensure you're using a Windows VM or Parallels, as .NET 4.8 isn't natively supported on macOS. Make sure **Rosetta 2** is installed for Intel-based application emulation. If the profiler still hangs on "connecting," check firewall settings and ensure the profiler can communicate with the VM.