microsoft / microsoft/MIEngine

C++ STL containers do not printed in pretty way if attached to process

Open
#1,221 7 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi

But its ok if start the process within VS2019 directly

Here is example with std::string

Directly started:
image

MI Logs:
image


Attached to the process started from bash:
image
image

MI Logs:
image

It can't parse any of stl container directly ;((

Please fix the issue

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

The issue names no source file or test; start by comparing the MI Logs for a process started in VS2019 with those from a process attached after starting from bash. Investigate why STL containers are not parsed or pretty-printed in the attached-process case, then verify that std::string and other STL containers display consistently after attachment.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.