Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slow speed when no breakpoints are set #160

Open
flipkickmedia opened this issue Feb 4, 2022 · 0 comments
Open

slow speed when no breakpoints are set #160

flipkickmedia opened this issue Feb 4, 2022 · 0 comments

Comments

@flipkickmedia
Copy link

flipkickmedia commented Feb 4, 2022

Executables

Bash Debug
v0.3.9

/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.

launch.json

 "configurations": [
    {
      "type": "bashdb",
      "request": "launch",
      "name": "Bash-Debug (simplest configuration)",
      "program": "/c/Users/tbmst/Documents/cme/usr/local/lib/cme/cme/cme.sh",
      "pathBashdb": "/usr/bin/bashdb",
      "cwd": "/c/Users/tbmst/Documents/cme",
      "pathBashdbLib": "/usr/share/bashdb",
      "terminalKind": "integrated",
      "showDebugOutput": true,
      "trace": true
    }
  ]

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant