App name:xx id:xx exited with code SIGSEGV, but no core dump generated.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
My app.js require some native module, so I hope to get core.dump file when my app crash with the signal SIGSEGV.
I have set global ulimit -c unlimited, and I checked it works OK, but it seems that with PM2, I cann't get core dump file.
I also try with https://github.com/ddopson/node-segfault-handler, but with PM2, nothing generated.
node version: 0.12.5
pm2 version: 0.12.16
Contributor guide
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 with the app.js case that requires a native module and reproduce a SIGSEGV under PM2 using the reported Node.js and PM2 versions. Compare the behavior with global core dumps enabled and with node-segfault-handler; the issue is done when a crashing PM2-managed app produces the expected core dump.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100