title: C++ entry points not showing up in node.js profiling output
body: <p>When running <code>node --prof &lt;command&gt;</code>, then later <code>node --prof-process</code> on macOS, my profiling output no-longer shows any of the C++ entry points, leading to a lot of unaccounted-for gaps in my profiling data. Changed around the same time, I now just see the <code>node</code> binary in these profiling trees where it wasn't showing up before, so it's like the profiler is no-longer able to "dive in" to the internals of node.</p>
  
  <p>I think this started when trying to improve dtrace permissions with <code>csrutil</code>, but I've restored things back to their factory settings and this still happens.</p>
  
  <p>What causes C++ entry points to not show up in traces? Is there a way to fix the issue?</p>
  
  <p><strong>Update</strong>:</p>
  
  <p>Just tried turning off SIP entirely with <code>csrutil disable</code> (which is a bad thing to do), and the problem persists, so maybe SIP is a red herring here.</p>