microsoft / microsoft/MIEngine
GDB exit code 139
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
Depending on where in my code I set breakpoints debugging sometimes works fine, sometimes everything hangs which can only be resolved by killing plink.exe (no timeout?) and sometimes I get this oscure error:
In this case I tried to circumvent the problem by setting a breakpoint programmatically. It brings up the dialog whether it should break or continue and after clicking either I get 139.
Debugging the program with gdb on Linux itself works fine.
Not sure what to do about it, quite a blocker.
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 with the issue reproduction: debug through MIEngine using GDB and plink.exe on the reported environment, varying breakpoint placement and comparing the Linux behavior. The issue mentions no source file or test; done means identifying why the session hangs or exits with code 139 and documenting or fixing that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100