Bug #21868: Prism doesn't use the ruby allocator

• Status: Closed
• Assignee: prism
• Target version: -
• Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN

[byroot (Jean Boussier)]

I discovered this while working on the internal side of [Feature #21861] (https://github.com/ruby/ruby/pull/15989)

Prism doesn't use ruby_xmalloc, but raw malloc.

I tried to fix it myself, but couldn't figure out the solution, so I left some FIXME comments:

• https://github.com/ruby/ruby/blob/d066b9e01ccb2260fac8b2580c10e73335c7c7db/prism_compile.c#L11333
• https://github.com/ruby/ruby/blob/d066b9e01ccb2260fac8b2580c10e73335c7c7db/vm_eval.c#L1779

I'd appreciate if someone from the Prism team could look at it.

[byroot (Jean Boussier)]

• Related to Feature #21861: C API: expose `ruby_xfree_sized`, `ruby_xrealloc_sized`, etc added

[Earlopain (Earlopain _)]

• Status changed from Open to Closed

Applied in changeset git|91be23cd961aa937701214ba5f50c698301c5e26.

---

[Bug #21868] Use ruby allocator for prism

If we wan't prism to use the ruby allocator, we should
include it as early as possible.