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

LogPoint stopped working v1.6.0 #8065

Closed
jakarman opened this issue Aug 27, 2021 · 4 comments
Closed

LogPoint stopped working v1.6.0 #8065

jakarman opened this issue Aug 27, 2021 · 4 comments
Labels
bug debugger fixed Check the Milestone for the release in which the fix is or will be available. regression A bug that didn't exist in a previous release

Comments

@jakarman
Copy link

jakarman commented Aug 27, 2021

Bug type: Debugger

  • OS and Version: Windows 10 Home

  • VS Code Version: 1.59.1

  • C/C++ Extension Version: 1.6.0

  • I just installed version 1.6.0, and the LogPoint functionality stopped working as it should. Instead of printing to the debug console, the message now stops as if it were a common breakpoint.

To Reproduce

  1. Create a simple file of C++
#include <iostream>
#include<windows.h>
using namespace std;

int main()
{
  while (1)
  {
    Sleep(1000);
    cout << "Hello World" << endl;
  }
    
}
  1. Compile the program
  2. Add a Logpoint at cout << "Hello World" << endl;
  3. Run the debugger.

Context

I'm using the default config for lauch.json to test the error. Using 1.5.1 works fine.

@WardenGnaw
Copy link
Member

Can you share your launch.json or share which debugger type you are using?

@WardenGnaw WardenGnaw added debugger more info needed The issue report is not actionable in its current state labels Aug 27, 2021
@jakarman
Copy link
Author

jakarman commented Aug 27, 2021

Hi,

I'm using GDB with the cppgdb

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "name": "g++.exe - Build and debug active file",
      "type": "cppdbg",
      "request": "launch",
      "program": "${fileDirname}\\${fileBasenameNoExtension}.exe",
      "args": [],
      "stopAtEntry": false,
      "cwd": "${fileDirname}",
      "environment": [],
      "externalConsole": false,
      "MIMode": "gdb",
      "miDebuggerPath": "D:\\Programas\\bin\\gdb.exe",
      "setupCommands": [
        {
          "description": "Enable pretty-printing for gdb",
          "text": "-enable-pretty-printing",
          "ignoreFailures": true
        }
      ],
      "preLaunchTask": "C/C++: g++.exe build active file"
    }
  ]
}

@WardenGnaw WardenGnaw added bug and removed more info needed The issue report is not actionable in its current state labels Aug 27, 2021
@WardenGnaw
Copy link
Member

This is a bug in v1.6.0. There will be a fix in the next release.

The current workaround is to use v1.5.1 if you need LogPoints.

@sean-mcmanus sean-mcmanus added the regression A bug that didn't exist in a previous release label Sep 1, 2021
@WardenGnaw WardenGnaw added the fixed Check the Milestone for the release in which the fix is or will be available. label Sep 10, 2021
@sean-mcmanus
Copy link
Collaborator

@jakarman jakarman closed this as completed Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug debugger fixed Check the Milestone for the release in which the fix is or will be available. regression A bug that didn't exist in a previous release
Projects
None yet
Development

No branches or pull requests

3 participants