Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Wrong exit-code parsing

Open
  • Is something wrong?
#1,328 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
devtools

Research direction

Start in DebuggedProcess.cs around lines 246-256 and compare the parser with the GDB output format shown in the issue. Done means exit codes formatted as octal by GDB are parsed correctly and the reported uint-size complaint is no longer triggered; verify against relevant debugger behavior.

Written by the indexing model from the issue text.

Description

See DebuggedProcess.cs, lines 246-256

GDB returns exit code as octal number, not decimal

      ui_out_field_fmt (uiout, "exit-code", "0%o", (unsigned int) exitstatus);

So:

  1. Parsing must be fixed
  2. Complains about exit code 'don't fit into uint' are baseless.
Dominant language
C#
Stars
859
Forks
233
Avg merge
4d 14h
Merged PRs (30d)
3

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/MIEngine

All issues in microsoft/MIEngine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.