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
{{ message }}
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.
Breakpoints can be set but are never hit.
All I get is the following output in VS Code's DEBUG CONSOLE.
Platform: win32
Launching program in terminal and waiting
Inactive RemoteSession
Remote debugger at "127.0.0.1:1358" connected at port 0.
Loading DB routines from perl5db.pl version 1.49_05
Editor support available.
Enter h or 'h h' for help, or 'perldoc perldebug' for more help.
main::(C:\Workspace\Designer 5\root\external_libs\netos-7.4.0.7/Clean.pl:8):
8: my $debug = 0;
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work. at C:/Perl64/lib/Term/ReadLine/readline.pm line 410.
at C:/Perl64/lib/Term/ReadKey.pm line 462.
Term::ReadKey::GetTerminalSize(IO::Socket::INET=GLOB(0x3279a40)) called at C:/Perl64/lib/Term/ReadLine/readline.pm line 410
readline::get_window_size called at C:/Perl64/lib/Term/ReadLine/readline.pm line 1117
readline::init called at C:/Perl64/lib/Term/ReadLine/readline.pm line 208
require Term/ReadLine/readline.pm called at C:/Perl64/lib/Term/ReadLine/Perl.pm line 65
eval {...} called at C:/Perl64/lib/Term/ReadLine/Perl.pm line 65
Term::ReadLine::Perl::new("Term::ReadLine", "perldb", IO::Socket::INET=GLOB(0x3279a40), IO::Socket::INET=GLOB(0x3279a40)) called at C:/Perl64/lib/perl5db.pl line 6864
DB::setterm() called at C:/Perl64/lib/perl5db.pl line 1845
DB::_DB__read_next_cmd(undef) called at C:/Perl64/lib/perl5db.pl line 2782
DB::DB called at C:\Workspace\Designer 5\root\external_libs\netos-7.4.0.7/Clean.pl line 8
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work. at C:/Perl64/lib/Term/ReadLine/readline.pm line 410.
The text was updated successfully, but these errors were encountered:
Correction. The breakpoints are being hit but there is no indication in the editor windows that this is the case. I guess the reason for that has something to do with the console dimension failures
Breakpoints can be set but are never hit.
All I get is the following output in VS Code's DEBUG CONSOLE.
Platform: win32
Launching program in terminal and waiting
Inactive RemoteSession
Remote debugger at "127.0.0.1:1358" connected at port 0.
Loading DB routines from perl5db.pl version 1.49_05
Editor support available.
Enter h or 'h h' for help, or 'perldoc perldebug' for more help.
main::(C:\Workspace\Designer 5\root\external_libs\netos-7.4.0.7/Clean.pl:8):
8: my $debug = 0;
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work. at C:/Perl64/lib/Term/ReadLine/readline.pm line 410.
at C:/Perl64/lib/Term/ReadKey.pm line 462.
Term::ReadKey::GetTerminalSize(IO::Socket::INET=GLOB(0x3279a40)) called at C:/Perl64/lib/Term/ReadLine/readline.pm line 410
readline::get_window_size called at C:/Perl64/lib/Term/ReadLine/readline.pm line 1117
readline::init called at C:/Perl64/lib/Term/ReadLine/readline.pm line 208
require Term/ReadLine/readline.pm called at C:/Perl64/lib/Term/ReadLine/Perl.pm line 65
eval {...} called at C:/Perl64/lib/Term/ReadLine/Perl.pm line 65
Term::ReadLine::Perl::new("Term::ReadLine", "perldb", IO::Socket::INET=GLOB(0x3279a40), IO::Socket::INET=GLOB(0x3279a40)) called at C:/Perl64/lib/perl5db.pl line 6864
DB::setterm() called at C:/Perl64/lib/perl5db.pl line 1845
DB::_DB__read_next_cmd(undef) called at C:/Perl64/lib/perl5db.pl line 2782
DB::DB called at C:\Workspace\Designer 5\root\external_libs\netos-7.4.0.7/Clean.pl line 8
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work. at C:/Perl64/lib/Term/ReadLine/readline.pm line 410.
The text was updated successfully, but these errors were encountered: