microsoft / microsoft/ProcDump-for-Linux
procdump doesn't exit after generating dump with -w
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.1k
- Forks
- 327
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
On GNU/Linux (tested with Debian 12 GNU/Linux), procdump (v3.4.1) doesn't exit after generating dump with -w.
If I run procdump -w app, procdump ends with [15:52:34 - INFO]: Stopping monitors for process: app (xxxx) after generating files, but never exits and I have to do Ctrl+C to exit. If -w is not provided, procdump exits without manual intervention
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
Reproduce the issue on GNU/Linux, such as Debian 12, with procdump -w app and compare it with a run without -w. Start by tracing the -w process-monitoring path after the dump is generated and the “Stopping monitors” message appears. Done means procdump exits automatically after generating the dump, without requiring Ctrl+C.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100