![]() ![]() This system using "man perl" or "perldoc perl". GNU General Public License, which may be found in the Perl 5 source kit.Ĭomplete documentation for Perl, including FAQ lists, should be found on Perl may be copied only under the terms of either the Artistic License or the (with 44 registered patches, see perl -V for more detail) This is perl 5, version 18, subversion 2 (v5.18.2) built for x86_64-linux-gnu-thread-multi The Lxss directory becomes visible only when you unhide 'protected operating system files'.īecause the applications installed there are the same binaries you find on a real Ubuntu system, you can't just launch them on Windows.Ĭ:\Users\lucvdv>C:\Windows\System32\bash.exe -c 'perl -version' ![]() The files can be found as explained here: When you "open file location" on that bash.exe in task manager it takes you to the Windows\system32 directory, but when you try the same on the actual bash or perl binary that is running in the Ubuntu subsystem, it doesn't take you anywhere at all, it doesn't open anything. That's logical, something has to provide the subsystem, the linux kernel those binaries think they're running under, just like there used to be a now-abandoned posix subsystem besides the win32 subsystem in older versions of Windows in the NT line. When I examine them in task manager, I see that there's a "microsoft bash launcher" (bash.exe) sitting between Windows and the Ubuntu binaries. UoW just might give the best result of all, if you can find a way to start the Ubunutu binaries from a windows process. I've tried cygwin (which seems to give the best results), Strawberry and ActivePerl, but what I haven't tried yet, is Perl in the new 'Ubuntu on Windows' subsystem that Microsoft and Canonical created together for Windows 10. ![]() But I think the problem is that all Windows versions of Perl have to compensate for the \r\n line ends in some way, and no two of them do it in the same way or to the same degree. I won't have much time to help debugging for the next month or so, and new projects will probably start popping up and interfering after that. With Strawberry Perl 64 bit, some output reached the debugger, but it was all error messages about not being able to determine the console window size and such, and it never reached the first breakpoint in the Perl code I was debugging (just a small test, barely above "hello world" functionality).ĭoes anyone have an idea of anything that might be tried to get around these problems? nothing), but I didn't check if perl.exe was launched in that case.īoth versions did work fine at a command prompt though. I tried ActiveState 64 bit with the same visible result (i.e. With ActiveState Community Perl 32 bit, it looks like the perl.exe executable is started, but no output from it ever reaches the debugger. I'm not a VS Code expert by far, but so far, I got this plug-in to work only with cygwin perl (I'm running Windows 10, BTW, and my cygwin is the 64 bit variety).Įven there it will step through code, but it won't let me examine variables.ĭid I misunderstand that variables don't work in mouse hover mode, but should appear in the 'variables' and 'watch' panes? The variables pane just remains empty, and adding anything in the watch pane doesn't give the expected result. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |