Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test debugging not possible #407

Open
davidefer opened this issue Mar 15, 2024 · 3 comments
Open

Test debugging not possible #407

davidefer opened this issue Mar 15, 2024 · 3 comments
Labels
C++ C++ Issue

Comments

@davidefer
Copy link

davidefer commented Mar 15, 2024

Installed product versions

  • Visual Studio: 2022 version 17.9.3
  • This extension: 1.1.213
  • Google test 1.12.2

Description

When the extension is enabled, I get several exceptions when i start the test debug session

Steps to recreate

  1. Enable the extension
  2. set a breakpoint in a google test
  3. in test explorer, debug the test
  4. several exceptions are thrown: breakpoint instruction executed (no file available), access violation in xstring line 398,

Current behavior

Debugging not possible when the extension is enabled

Expected behavior

One should be able to debug the tests also if the extension is enabled

Side Notes

  • when the extension is disabled, debugging is possible with no problems
@davidefer davidefer changed the title Test debuggin not possible Test debugging not possible Mar 15, 2024
@tonyhallett
Copy link
Collaborator

C++ is not properly supported. The extension is made for C# and VisualBasic.

I am not sure if this is FCC related. From https://learn.microsoft.com/en-us/troubleshoot/developer/visualstudio/ide/troubleshooting-code-coverage
( which is not using FCC )

For C++ projects, ensure that the generated .pdb files have full debug information. Open the project properties and verify that Linker > Debugging > Generate Debug Info is set to Generate Debug Information optimized for sharing and publishing (/DEBUG:FULL).

Does this help ?

@davidefer
Copy link
Author

Hi Tony
no it doesn't help for the exception but it was anyway helpful because now I see the proper coverage in my source file (before it was not completely correct).
Actually the C++ support is not bad at all, but I've not tested thoroughly.
Thank you!

@tonyhallett
Copy link
Collaborator

Although not related to this issue I thought that you might want to check thise section
https://learn.microsoft.com/en-us/visualstudio/test/customizing-code-coverage-analysis?view=vs-2022#static-and-dynamic-native-instrumentation

@tonyhallett tonyhallett added the C++ C++ Issue label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C++ C++ Issue
Projects
None yet
Development

No branches or pull requests

2 participants