1

I'm trying to use the immediate windows in C++ at runtime. The Relevant documentation in MSDN is here

enter image description here

I saw this question also. But is is not yet solved and related to C#.

Community
  • 1
  • 1
user2346536
  • 1,464
  • 2
  • 21
  • 43
  • Don't post pictures of text. Post the text. – molbdnilo Feb 03 '16 at 13:24
  • I'll have to guess that you are using VS2015. It has a new native debugging engine, the legacy Windbg style commands are pretty broken. Tools > Options > Debugging > General > tick the "Use Native Compatibility Mode" option to revive it. – Hans Passant Feb 03 '16 at 13:48
  • @HansPassant , I'm using VS Professional 2013 – user2346536 Feb 03 '16 at 14:10
  • 1
    Always select the VS version you use when looking at MSDN documentation. That VS2013 is not listed is not an accident. It also has a new debugging engine, the one that supports the new natvis visualizers. But not the option to fall back to the legacy engine. Bummer. Use Windbg. – Hans Passant Feb 03 '16 at 14:15
  • MSDN: "This option is valid only for C++ projects in runtime mode." – zdf Feb 03 '16 at 16:44
  • @ZDF; Am I not in runtime mode when debugging ? – user2346536 Feb 04 '16 at 16:57
  • @HansPassant , thanks, I guess I'll do without it. – user2346536 Feb 04 '16 at 16:57
  • @user2346536 I am not sure on the exact meaning of MSDN comment. It seems to refer to a kind of project, not to a state. The comment is not present on ".K (Display Callstack)" help page. If you go to Immediate Window and enter `>S`, a list with available commands will pop-up. `S` is not among them, therefore I believe that it was removed. `K` works. – zdf Feb 04 '16 at 17:33
  • @user2346536 Maybe Microsoft was unable to fix problems like [this](https://connect.microsoft.com/VisualStudio/feedback/details/845091/debugging-memory-search-command-in-immediate-window-is-broken-with-large-values) and decided to remove it (notice the status). – zdf Feb 04 '16 at 17:37

0 Answers0