ml-explore / ml-explore/mlx-swift
LLDB hanging when doing po on mlx-swift objects
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2k
- Forks
- 349
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 13
Description
I am using LLDB to debug some model code that I have written in mlx-swift. Unless I do an explicit eval() or print() before doing a po on the object in question, LLDB will hang. Is this behavior expected with lazy evaluation?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the LLDB po hang with mlx-swift objects, comparing cases with and without an explicit eval() or print(). Investigate the lazy-evaluation interaction described in the issue; done means establishing whether the behavior is expected and identifying the relevant fix or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- developer-experience, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100