Add "profiling" cargo build profile

[brooksprumo]

Problem

Building binaries designed for profiling (optimizations ON, debug symbols ON) could be easier.

Summary of Changes

Add a new cargo build profile, "profiling", which inherits from "release" and enables debug symbols.

To use:

$ cargo build --profile profiling --bin solana-validator

Also open to other names. Specifically, should the profile be the intent (i.e. "test", "bench", "release", "debug"), or the details (i.e. "release-with-debug-symbols")? As you can see, I've gone with the intent-side. But I acknowledge that --profile profiling isn't the best.

[codecov]

Codecov Report

Merging #24343 (f6b84d0) into master (b9caa8c) will decrease coverage by 0.0%.
The diff coverage is 86.6%.

@@            Coverage Diff            @@
##           master   #24343     +/-   ##
=========================================
- Coverage    82.1%    82.1%   -0.1%     
=========================================
  Files         582      582             
  Lines      162041   162383    +342     
=========================================
+ Hits       133132   133384    +252     
- Misses      28909    28999     +90     

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[KirillLykov]

Would be nice to specify there also compiler option -C force-frame-pointers=y' to prevent getting rid of frame pointer. This allows sampling with stack information for perf.

[brooksprumo]

Would be nice to specify there also compiler option -C force-frame-pointers=y' to prevent getting rid of frame pointer. This allows sampling with stack information for perf.

Yes, I agree. That's why this PR has gone stale; I don't know of a way to add these rustc flags to a profile. I was hoping to effectively have:

RUSTFLAGS="-g -C force-frame-pointers=y -C target-cpu=native"

[KirillLykov]

Would be nice to specify there also compiler option -C force-frame-pointers=y' to prevent getting rid of frame pointer. This allows sampling with stack information for perf.

Yes, I agree. That's why this PR has gone stale; I don't know of a way to add these rustc flags to a profile. I was hoping to effectively have:

RUSTFLAGS="-g -C force-frame-pointers=y -C target-cpu=native"

Looks like it is possible to create a .cargo/config file and specify flags there, yet seems that this feature doesn't always work well see

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This stale pull request has been automatically closed. Thank you for your contributions.