Exit with code 14 instead of continuing
Open
Nobody has claimed this yet.
bug
functionality
Impact: Medium
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Using Debian Linux and version Binary Ninja 4.0.4911 free
- Load file
- Create breakpoint
- Start debugging
- Resume from initial breakpoint at entry
- Interact in console with program
- Hit breakpoint
- Create stack view and interact with stack view
- Resume
- Exits with code '14' instead of further interaction with console
Does not reproduce consistently. Sometimes does resume and interact as expected, then shows exit with code 0. Actual debugged program main returns %eax if equal to zero only.
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 listed breakpoint, console, stack-view, and resume sequence on Debian Linux with Binary Ninja 4.0.4911, recording when exit code 14 occurs versus code 0. Compare the debugger behavior after interacting with the stack view and determine what condition causes the debugged program to terminate instead of continuing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, linux
- Domain
- devtools, operating-systems, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100