You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
@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.
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:
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?
The text was updated successfully, but these errors were encountered: