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

Displaying only the first argument of variadic template in debugger #7075

Closed
BOT-Man-JL opened this issue Mar 1, 2021 · 3 comments
Closed
Labels
debugger investigate: repro This issue's repro steps needs to be investigated/confirmed

Comments

@BOT-Man-JL
Copy link

BOT-Man-JL commented Mar 1, 2021

Type: Debugger

Describe the bug

  • OS and Version: Windows 10 19041
  • VS Code Version: 1.53.2
  • C/C++ Extension Version: 1.2.2
  • Other extensions you installed (and if the issue persists after disabling them): Non.
  • Discription:
    • Displaying only the first argument of variadic template in variables view or hover tooltip.
    • But it's available in Visual Studio (with the same argument name but different param types).

image

To Reproduce
Please include a code sample and launch.json configuration.
Steps to reproduce the behavior:

  1. Debugging C++ code with variadic template.
  2. See error

image

image

image

Additional context
If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json
Add any other context about the problem here including log or error messages in your Debug Console or Output windows.

@WardenGnaw
Copy link
Member

Which debugger are you using cppdbg or cppvsdbg and if possible can you provide logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json

@WardenGnaw WardenGnaw added debugger investigate: repro This issue's repro steps needs to be investigated/confirmed labels Mar 1, 2021
@github-actions
Copy link

This issue has been closed automatically because it has not had recent activity.

@BOT-Man-JL
Copy link
Author

Which debugger are you using cppdbg or cppvsdbg and if possible can you provide logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json

@WardenGnaw Sorry for missing the message... I was using the cppvsdbg option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debugger investigate: repro This issue's repro steps needs to be investigated/confirmed
Projects
None yet
Development

No branches or pull requests

2 participants