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

Unable to start debugging. UseShellExecute must be false when redirecting I/O. #1756

Closed
paulmadejong opened this issue Mar 29, 2018 · 5 comments
Assignees
Labels
bug debugger fixed Check the Milestone for the release in which the fix is or will be available.

Comments

@paulmadejong
Copy link

paulmadejong commented Mar 29, 2018

Today, after switching workspaces, my VSC reported an error "command 'extension.cppdbgAdapterExecutableCommand' not found. when trying to debug my C code that worked fine just before. After reinstalling and following the steps in #1605 I no longer get said message but a new one when debugging:

Unable to start debugging. UseShellExecute must be false when redirecting I/O.

At this point, I can no longer debug my code even after reinstalling the cpptools extension several times. Restarting my system didn't help either. The same extensions and versions running on my CentOS7 VM works fine. It's just my MBP that is no longer working.

I just noticed that this only happens when the MIMode is set to "gdb". With "lldb" it works but I cannot debug my fortran code part of the workspace. Running gdb from command line on the same executable works fine though. Any ideas?

  • OS: MacOS High Sierra
  • VSC: 1.21.1
  • cppTools; 0.16.0
  • Extensions: Bash Debug, C/C++/ C/C++ Clang Command Adapter, CMake, CMake Tools, Hg, Modern Fortran, Native Debug, Python
@pieandcakes
Copy link
Contributor

@paulmadejong This seems to be an issue that was introduced when @WardenGnaw was fixing the stdout/stderr redirection problem that manifested itself with Invalid json. Unfortunately you might need to rollback to installing the offline package for OS X for the previous release until we can ship an update with this fix.

@sean-mcmanus sean-mcmanus added this to the 0.16.1 Bug Fix Release milestone Mar 30, 2018
@Cheng-SG
Copy link

Encounter the same problem! would you please fix this as soon as possibile? Many thanks!

@coisme
Copy link

coisme commented Mar 30, 2018

+1

@paulmadejong
Copy link
Author

Reverting to 0.15.0 using the VSIX installer worked for me while waiting for the fix to be released. Thanks!

@sean-mcmanus sean-mcmanus added the fixed Check the Milestone for the release in which the fix is or will be available. label Mar 30, 2018
@WardenGnaw
Copy link
Member

WardenGnaw commented Mar 31, 2018

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.
Projects
None yet
Development

No branches or pull requests

6 participants