PennyLaneAI / PennyLaneAI/catalyst
`import`ing `cudaq` before executing a lightning kokkos kernel triggers a segmentation fault
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 234
- Forks
- 84
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 66
Description
This appears to be caused by cudaq linking against some libraries at import time. These libraries have some symbols set to be externally visible. Lightning kokkos uses some of this symbols, so when lightning kokkos execute, cudaq symbols will be used. This issue can be reproduced without catalyst. This will be solved when moving to manylinux 2 28 or potentially could be fixed upstream by in the cudaq package.
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
Reproduce the failure by importing cudaq before executing a lightning kokkos kernel, as described in the issue. Investigate the package's import-time library linking and the manylinux 2_28 migration or upstream cudaq package; done means the kernel no longer segfaults in the stated order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100