cgo pkg-config in non-instrumented dependency stops godebug cold
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
If some distant dependency is linked to native code, why does godebug object with error
cgo pkg-config not supported couldn't load packages due to errors:
Then the file I want to debug won't build because symbols can't be found.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by reproducing the failure with a target that has a distant native dependency using cgo and pkg-config, then trace where godebug stops loading packages. Done means the target builds and can be debugged without the non-instrumented dependency blocking symbol resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100