diff options
| author | Alan Wu <XrXr@users.noreply.github.com> | 2025-12-16 13:33:47 -0500 |
|---|---|---|
| committer | Alan Wu <XrXr@users.noreply.github.com> | 2025-12-16 14:56:40 -0500 |
| commit | eaa952b536c48658a5a2e3f128e3afdef03a01b6 (patch) | |
| tree | 419c881eb033b28d67eeee6bf4c4ecbb9565cb1f /include/ruby/internal | |
| parent | f3d1557d5c04d7bc0bfa931869fbb35d14592c53 (diff) | |
YJIT: Print `Rc` strong and weak count on assert failure
For <https://bugs.ruby-lang.org/issues/21716>, the panic is looking like
some sort of third party memory corruption, with YJIT taking the fall.
At the point of this assert, the assembler has dropped, so there's
nothing in YJIT's code other than JITState that could be holding on to
these transient `PendingBranchRef`.
The strong count being more than a handful or the weak count is non-zero
shows that someone in the process (likely some native extension)
corrupted the Rc's counts.
Diffstat (limited to 'include/ruby/internal')
0 files changed, 0 insertions, 0 deletions