vscode-bash-debug
vscode-bash-debug copied to clipboard
Step-Over not hitting breakpoints in Bash function
Using Bash Debug plugin version 0.3.8 with VSCode 1.45.1 on Ubuntu 18.04 Linux.
Using /bin/bash
Linux centipede-dev 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
---
/bin/bash
GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://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.
---
bash: bashdb: command not found
---
/bin/cat
cat (GNU coreutils) 8.28
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://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
mkfifo (GNU coreutils) 8.28
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://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
pkill from procps-ng 3.3.12
The launch.json file:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "bashdb",
"request": "launch",
"name": "Bash-Debug (simplest configuration)",
"program": "${file}"
}
]
}
Details
If I set a breakpoint in a function and am stepping through the script, if I step-over the function the breakpoint is not hit. I don't think this is the expected behavior. Working with other debuggers i know that when you step-over a function which would hit an instruction which has a BP set on it should cause the debugger to stop at the BP.
If this is a bug it should be addressed.
Thank you, Michael Uman AI Acceleration Engineer IBM
As far as I recall, this was an issue with bashdb scripts. I will try to check this though...