microsoft / microsoft/MIEngine

Wrong exit-code parsing

Open
#1,328 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
859
Forks
233
Avg merge
1d 6h
Merged PRs (30d)
3

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.

Contributor guide

No contributing guide indexed for this repository

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.

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.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.