ruby / ruby/fiddle

Closing `DEFAULT` or `NEXT` can crash Ruby

Open
#207 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
195
Forks
53
Avg merge
23h 57m
Merged PRs (30d)
1

Description

Yet another bug report based on some rough AI-assisted investigation.

require "fiddle"

Fiddle::Handle::DEFAULT.close
Fiddle::Handle::NEXT.close

Both are pseudo-handles for symbol lookup, not real dlopen() handles. They must not be passed to dlclose().
Expected: raise an exception or do nothing.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Fiddle::Handle::DEFAULT.close and Fiddle::Handle::NEXT.close examples, then trace the Fiddle::Handle#close entry point and its handling of pseudo-handles. Done means neither call reaches dlclose() unsafely, and regression coverage verifies that each call raises an exception or does nothing.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.