Björn Höhrmann
Björn Höhrmann
@drq883 : Which version of the extension? Have you tried enabling the `debugRaw` setting in `launch.json`? The output could give us a clue what is going on.
@drq883 : Sounds like https://github.com/raix/vscode-perl-debug/issues/75 which was fixed in 0.6.0 released yesterday. Could you upgrade and try again?
@remicharleslageixarena : Could you give 0.6.0 a try? @drq883 : Very possible that 0.6.0 ignores the setting and always generates that output window, I believe I fixed something like that...
@JB62: You could enable the `debugRaw` option in your `launch.json`. It would show the communication between the extension and the Perl debugger, maybe that gives a clue (e.g., what the...
Note that the Travis-CI failures for OS X are bogus, https://travis-ci.org/raix/vscode-perl-debug/jobs/514878456 for instance is supposed to test Perl 5.22, but ends up using Perl 5.18 like all tests do for...
@raix: It does not remove the need for PadWalker, but does improve a number of things... Okay, will try to update the PR.
@raix: Give this a try. Test suite passes locally at least, and cursory check in vscode suggests it is still working, I also made one change that made me say...
@raix: any feedback?
Which version of the extension? Could you enable the `launch.json` setting `debugRaw` and have a look at the corresponding output window (possibly send in its contents)? Also, do a `p...
Possibly fixed by #91