segfault on setup with no params
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
I can reliably produce a segfault by running a proto script with
proto_x_setup() {
local config="$1"; shift
...
proto_run_command "$config"
}
kern.info: [341953.079132] netifd[20778]: segfault at 0 ip 00007fc4a52f5345 sp 00007ffea5432b30 error 4 in libc.so[5b345,7fc4a52ae000+58000] likely on CPU 0 (core 0, socket 0)
kern.info: [341953.145301] Code: 02 00 48 83 ec 58 64 4c 8b 34 25 28 00 00 00 4c 89 75 c8 49 89 d6 67 e8 5c 44 fe ff 49 89 c7 e8 ec 47 fe ff c7 00 02 00 00 00 <80> 3b 00 74 77 49 89 c4 be 2f 00 00 00 48 89 df 67 e8 26 95 00 00
Options shall be present for the proto handler to be useful, but it seems there are no checks that they are present.
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 segfault with the shown proto_x_setup script and no parameters, then inspect the proto handler path around proto_run_command. Use the attached netifd core dump to identify the failing path; done means the no-parameter case no longer segfaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100