gpio exits on module reload and segfaults
Open
- Dominant language
- Erlang
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
While developing code, I use rebar3 auto. After compiling some code changes, the process which opened a gpio line event gets a {‘EXIT’, _, killed}. On receiving the EXIT, I stop the controlling process so the its supervisor can restart it. However, I get a seqfault now.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the module-reload scenario described in the issue with rebar3 auto, where a GPIO line event process receives an EXIT and the supervisor restarts it. Trace the GPIO event process and its shutdown path; done means the process can be restarted after reload without a segmentation fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100