Error getting stack trace

[alanbirtles]

When trying to get the stack trace after stopping at a breakpoint or exception visual studio code is throwing a NullReferenceException.
I'm running cpptools 0.14.4 on Centos 7 in vs code 1.18.1
stack trace of error:
stacktrace.txt

[nzjony]

I also started having a similar problem starting today, please see image:

I'm running also running cpptools 0.14.4, Ubuntu 16.04 with code 1.18.1

[pieandcakes]

Can either of you tell me if this is 100% reproducible and what the steps are to hit this?

[pieandcakes]

I have CentOS 7 with 0.14.4 installed with a multithreaded C++ app. I have set breakpoints and also hit pause to try and replicate this and i'm not able to.

[sean-mcmanus]

I also am not able to repro this on Mint/Ubuntu 16.04. Do you have a breakpoint in some file "special" file or is there anything else unusual about your scenario? What is your debugger type? gdb?

[alanbirtles]

I don't know how to reproduce it but I was unable to hit these breakpoints all day, this was with gdb

[pieandcakes]

Ok. I think I might have figured out what the problem is. The log file helped out immensely. I'm going to see if I can make a fix.

[pieandcakes]

@alanbirtles @nzjony Can either of you try this release and see if it fixes the problem?
Steps:

1. Download the file.
2. Uninstall the existing extension.
3. Go to Extensions -> ... -> Install from VSIX and choose the file that was downloaded.

It should prompt you to reload. Then try debugging.

Please let me know.

Thanks

[pieandcakes]

Can anyone confirm if this fixes their issue? I would like to know if I need to investigate more. Thanks!

[ytimenkov]

@pieandcakes I've had similar issue when debugging remote target on CentOS 7.4 (debugger just failed to show any call stack and execute any command when execution stopped at breakpoint).

With 0.14.5-insiders release the problem is gone and debugger started working again.
Thanks for quick fix!

[alanbirtles]

seems to work for me too

[alexbaden]

Resolved here, Arch w/ code 1.18.1.

[josesimoes]

I stumbled on this today too. Installed the fix from @pieandcakes and it's gone.
If this is relevant I'm using VS Code on a Windows 10 64bits setup.

[pieandcakes]

We're probably releasing this fix next week with a few other bugfixes.

[sean-mcmanus]

Fixed with 0.14.5.