Use spans in base StackTrace and enable more unsafe-buffer-usage

Enable unsafe buffer warnings in a few files in base, which turned up
a rabbit hole to spanify the StackTrace code. Instead of working with
void**, work with span<void*> and remove the explicit size parameters.

Remove TraceStackFramePointersFromBuffer as its only caller was from
unit tests, and remove the test case that was calling it.

Bug: 40284755
Change-Id: Ibaeaee08acf951025ec5a090b12a60f49b86f5e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5740744
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Owners-Override: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: danakj <danakj@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1333759}
NOKEYCHECK=True
GitOrigin-RevId: e75c6c812282a4268d067c09a5bf6c9d272ca557
1 file changed
tree: 3e8e95821e8de7210f00c9e1cfe7268bd5f1fce9
  1. custom/
  2. .gitignore
  3. BUILD.gn
  4. DEPS
  5. DIR_METADATA
  6. OWNERS
  7. README.chromium