JJenkxandClaude Opus 5.5 3316ca3b24 feat(libc): list the reporting thread's own calls in the call trace report ...

The crash and abort reports printed the last 64 traced calls of the whole
process, so a thread that loops on a traced import (a mutex lock/unlock
pair, a profiler marker) pushes the calls of the faulting thread out of the
report. The ring already keeps the last 65536 calls with their thread.

CopyThreadCallTrace_nid_no_patch returns the most recent calls of one
thread from that ring, oldest first, and both reports (Windows crash and
abort, Linux abort) list up to 32 of them for the reporting thread after
the process-wide list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-20 20:25:31 -04:00

..

INPUT_MAPPING.md

Merge pull request #3998 from MrMha/feat/controller-timelines

2026-10-21 04:08:30 +13:00

USAGE.md

feat(libc): list the reporting thread's own calls in the call trace report

2026-10-20 20:25:31 -04:00