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
/usr/bin/bash
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
bashdb, release 5.0-1.1.2
cat (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law.
Written by Torbjorn Granlund and Richard M. Stallman.
---
/usr/bin/mkfifo
/bin/mkfifo
mkfifo (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David MacKenzie.
---
/usr/bin/pkill
/bin/pkill
pkill from procps-ng 3.3.16
Debug output
There is a huge amount. I'm not sure you will need it. I'm not seeing any errors or any loops etc.
I can step through the code faster (holding step over key down) than if I just leave it the script to run without setting breakpoints.
This is a fairly large script and involves a lot of setting vars and indirect var referencing.
This is being run inside inside WSL, as the breakpoints fail to work when running this from Windows. When running in Windows the script runs very quickly. I see commands run, only a few a second second whilst leaving the script to run normally during debugging as opposed to 50 or so per second whilst stepping through holding the step over key.
Advice on how to further diagnose the problem would be appreciated.
The text was updated successfully, but these errors were encountered:
Executables
Bash Debug
v0.3.9
Debug output
There is a huge amount. I'm not sure you will need it. I'm not seeing any errors or any loops etc.
launch.json
Details
I can step through the code faster (holding step over key down) than if I just leave it the script to run without setting breakpoints.
This is a fairly large script and involves a lot of setting vars and indirect var referencing.
This is being run inside inside WSL, as the breakpoints fail to work when running this from Windows. When running in Windows the script runs very quickly. I see commands run, only a few a second second whilst leaving the script to run normally during debugging as opposed to 50 or so per second whilst stepping through holding the step over key.
Advice on how to further diagnose the problem would be appreciated.
The text was updated successfully, but these errors were encountered: