Odd fork/exec/pthread interaction behavior
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 420
- Forks
- 80
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 9
Description
It appears that some interaction between pthreads and fork/exec is causing caliper to emit records in the child during the exec phase as well as in the parent, causing duplicate records in the output. A small reduced example using just fork and exec does not exhibit this behavior, so it may be related to finalization methods on a per-thread basis.
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
No source files, tests, or entry points are named. Start by reproducing the fork/exec/pthread interaction and compare records emitted by the parent and child during exec, then trace per-thread finalization. Done means the child no longer emits duplicate records while the parent behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100