microsoft / microsoft/vscode-cpptools

Evaluate doesn't work as expect during core dump debugging

Open
#500 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug debugger
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Configuration:

Ubuntu 14 x64 + Cpptools 20160720.1

VSCode : 1.3

Repro Steps:

  1. Copy the source code from
    main.zip

  2. Compile the source: g++ -g exception.cpp main.cpp -o myapp

  3. Enable the core dump: ulimit -c unlimited

  4. Launch the application to generate the core dump:

    ./myapp "-CallRaisedUnhandledException"

  5. Configure the launch.json for "program" and "coreDumpPath"

  6. F5

  7. Try to evaluate:

    a) result = result +1

    b) EvalFunc(100,100)

Actual:

In both cases, it just returns "not available"

Expected:

a) For result = result +1, I assume the evaluated result should be "11" ?

b) For EvalFunc(100,100) - I have a dar automation test which should verify the error message for function evaluation during core dump debugging, just want to double confirm the message "not availabe" is correct ? I assume it should be similar like "Function evaluation is not supported during core dump debugging? "

Investigation:

You can refer to attached MIEngine log

Contributor guide

Open the contributing guide

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 by reproducing the core-dump session with the attached main.zip source, Ubuntu, and a launch.json using program and coreDumpPath. Review the attached MIEngine log while evaluating the assignment and function call; done means the behavior and expected error message are established or the reported evaluation problem is fixed and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.