cargo: build with frame pointers

[erikgrinaker]

Problem

Frame pointers are often disabled by default (depending on the architecture), since this frees up an additional CPU register. However, this makes stack unwinding more difficult, and it often has to rely on DWARF debug information which is very slow. With continuous profiling, cheaper stack unwinding will likely be a net win, and allow us to use higher sampling resolution.

This may cause some performance loss (TODO: benchmark), but typically <1% on 64-bit architectures. aarch64 architectures (used for Pageservers) also typically mandate the use of a dedicated frame pointer register, so this has no effect.

Resolves #10224.

Summary of changes

Enable frame pointers in all builds.

[github-actions]

7095 tests run: 6798 passed, 0 failed, 297 skipped (full report)

---

Code coverage* (full report)

• functions: 31.2% (8398 of 26877 functions)
• lines: 48.0% (66682 of 139059 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
c89b06c at 2024-12-22T22:59:42.539Z :recycle:}