microsoft / microsoft/MIEngine

Specific -var-create in core dump debugging is incredible slow

Open
#1,479 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

Hello.

Summary
Debugging a C++ Core dump spent too much time waiting for the result of an specific -var-create (cutFrames).

The context is explained in this thread in C++ debugger extension.

GDB command line does not suffer of this problem, overall debug took ~2 minutes.

Gathering debug info from MIENGINE

I was able to setup the debugger to debug OpenDebugAD7 process.

  • Stepping through the code flow

https://github.com/microsoft/MIEngine/blob/074837ed159e41a3e550b41eb99cdc22d97ab519/src/MIDebugEngine/Engine.Impl/DebuggedProcess.cs#L2055

  • Command: 1106-var-create - * "cutFrames"
  • After executing the CmdAsyncInternal I lost what's going on:

https://github.com/microsoft/MIEngine/blob/074837ed159e41a3e550b41eb99cdc22d97ab519/src/MICore/Debugger.cs#L875-L887

imagen

  • Nexts steps shows a ParseIssue? for it also shows the same for the other args (which seems to respond quickly)
    imagen

Could you help me to identify what's going on? Any idea?
Thanks.

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 with the -var-create command flow in src/MIDebugEngine/Engine.Impl/DebuggedProcess.cs and follow CmdAsyncInternal in src/MICore/Debugger.cs. Inspect the wait in src/MICore/Transports/StreamTransport.cs while reproducing the core-dump case, then compare the slow request with the other arguments. Done means identifying the cause of the delay and documenting or fixing the affected behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.