panic in HashTrieMap
Open
Nobody has claimed this yet.
- Dominant language
- LLVM
- Stars
- 758
- Forks
- 49
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 138
Description
package main
import (
"os"
)
func main() {
os.Exit(1)
}
Program received signal SIGSEGV, Segmentation fault.
#0 0x00000000002428e6 in internal/sync.(*HashTrieMap[any,any]).initSlow ()
#1 0x0000000000243bf3 in internal/sync.(*HashTrieMap[any,any]).Range ()
#2 0x000000000023f602 in internal/godebug[update] ()
#3 0x0000000000246e26 in internal/godebug[setUpdate] ()
#4 0x000000000023ef23 in internal/godebug[init] ()
#5 0x0000000000225c26 in time[init] ()
#6 0x00000000002239a9 in io/fs[init] ()
#7 0x00000000002238df in internal/filepathlite[init] ()
#8 0x00000000002151d6 in os[init] ()
#9 0x0000000000215073 in main ()
llgo v0.13.1-0.20260603081057-a65b6c7e4aea linux/amd64
built from this repo manually
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
Start by reproducing the provided os.Exit(1) program with llgo on linux/amd64 and inspect the stack trace. Trace the internal/sync.HashTrieMap initSlow and Range calls shown in the report, along with internal/godebug initialization. Done means the program no longer segfaults during startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100