[Bug Report] WARN handlePkt: qName cannot be empty
- Dominant language
- Go
- Stars
- 6.2k
- Forks
- 402
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 1
Description
### Checks
- [X] I have searched the existing issues
- [X] I have read the documentation
- [X] Is it your first time sumbitting an issue
### Current Behavior
[Jan 26 16:01:33] WARN handlePkt: qName cannot be empty
[Jan 26 16:01:33] WARN handlePkt: qName cannot be empty
[Jan 26 16:01:33] WARN handlePkt: qName cannot be empty
[Jan 26 16:01:33] WARN handlePkt: qName cannot be empty
[Jan 26 16:01:33] WARN handlePkt: qName cannot be empty
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x473c80]
goroutine 2367441 [running]:
errors.(*errorString).Error(0xe03900?)
errors/errors.go:71
github.com/daeuniverse/dae/control.(*DnsController).dialSend.func2()
github.com/daeuniverse/dae/control/dns_control.go:597 +0x5a2
created by github.com/daeuniverse/dae/control.(*DnsController).dialSend in goroutine 2366327
github.com/daeuniverse/dae/control/dns_control.go:584 +0x129f
跑一阵子后就会这样子结束程序
### Expected Behavior
_No response_
### Steps to Reproduce
_No response_
### Environment
- **Dae version (use `dae --version`)**: dae version v0.5.1
- **OS (e.g `cat /etc/os-release`)**: Debian GNU/Linux 10 (buster)
- **Kernel (e.g. `uname -a`)**: Linux debian10A 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
- **Others**:
### Anything else?
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading control/dns_control.go around lines 584-597 and the stack-trace entry at errors/errors.go:71, then review the reported WARN messages and nil-pointer panic under dae v0.5.1 on Debian 10. The issue is done when the reported long-running DNS scenario no longer terminates the process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100