panic: NewTypeDecl: fail to complete type string_descriptor_zero: unsupport field with array without length
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 33
- Forks
- 11
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 51
Description
struct string_descriptor_zero {
uint8_t bLength;
uint8_t bDescriptorType;
uint16_t wBcdLang[];
} __packed;
panic: NewTypeDecl: fail to complete type string_descriptor_zero: unsupport field with array without length
goroutine 1 [running]:
main.check(...)
/Users/xxx/project/llcppg/cmd/gogensig/gogensig.go:134
main.main()
/Users/xxx/project/llcppg/cmd/gogensig/gogensig.go:102 +0x724
panic: exit status 2
goroutine 1 [running]:
main.check(...)
/Users/xxx/project/llcppg/cmd/llcppg/llcppg.go:195
main.do({0x1006fec52, 0xa}, 0x3, 0x7, {0x16f803037, 0x8})
/Users/xxx/project/llcppg/cmd/llcppg/llcppg.go:189 +0x30c
main.main()
/Users/xxx/project/llcppg/cmd/llcppg/llcppg.go:161 +0x408
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
Reproduce the failure with the shown struct, then inspect the NewTypeDecl path reported by cmd/gogensig/gogensig.go:134 and cmd/llcppg/llcppg.go:195. Determine how an array without a length should be handled and add or update coverage if the repository provides a relevant test location; done means this input no longer exits with the shown panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100