vm_dump.c: note when there is no Ruby execution contextHEADmaster

rb_vm_bugreport() silently skipped the control frame information, Ruby
level backtrace, and threading sections when vm or ec was NULL, so the
report jumped straight to the machine register context with no explanation
of why no Ruby level information was shown. ec can be NULL for various
reasons (e.g. a process-directed signal delivered to a non-Ruby thread, or
simply a window where the current thread has no execution context yet).

Emit an explicit note under the "Control frame information" header in that
case, without speculating about the cause. This makes the report
self-explanatory and keeps the section present, so test_crash_report no
longer fails intermittently when ec happens to be NULL.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions