Crash in `examples/test-e.rb:52` (and -j.rb)

[skull-squadron]

Running with scissors in the dark, I would guess there's a missing check or API change somewhere. Removing the line allows the demo to run, albeit with missing intended behavior. The other demos work fine.

Running lldb ruby examples/test-e.rb

Process 21806 stopped                                                      │
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x9)
    frame #0: 0x00000001008141c4 libruby.3.1.dylib`rb_cvar_set [inlined] cvar_lookup_at(klass=4305990040, id=56193, v=0x0000000000000000) at variable.c:3401:10                                                  │
   3398  static int                                                        │
   3399  cvar_lookup_at(VALUE klass, ID id, st_data_t *v)                  │
   3400  {                                                                 │
-> 3401      if (!RCLASS_IV_TBL(klass)) return 0;                          │
   3402      return st_lookup(RCLASS_IV_TBL(klass), (st_data_t)id, v);     │
   3403  }                                                                 │
   3404  │                                                                 │
Target 0: (ruby) stopped.

Crash log

Here's the .ips

One of the working demos

---

[lzap]

Full disclosure: our team is maintaining the library so it does compile on modern systems, however, don't expect much work on the examples front. There are bugs indeed, most of them on non-Linux platforms.

[rtgill82]

I'm getting this issue too. My distro now defaults to ruby 2.7. I don't think the issue occurred with ruby 2.6. I'll look into it.

[skull-squadron]

Cool. If I have time, I'll step through it in debug Ruby builds 2.6, 2.7, and 3.1 on the weekend too.

[rtgill82]

@steakknife Changes have been merged that seem to fix the issue under Linux. Would you be able test the most recent changes under macOS?

[rtgill82]

I've tested this on macOS Monterey with ruby 3.1.3 and it seems this issue has been resolved. Although I've discovered there are warnings when built against ruby 3.2.0.