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

superbol-vscode-debug bug: empty prelaunch task does not work #325

Open
GitMensch opened this issue Jul 25, 2024 · 0 comments
Open

superbol-vscode-debug bug: empty prelaunch task does not work #325

GitMensch opened this issue Jul 25, 2024 · 0 comments
Labels
debugger Specific to the debugger extension

Comments

@GitMensch
Copy link
Contributor

GitMensch commented Jul 25, 2024

I've dropped the configured preLaunch task as I don't want to run this each time I start the debugger.
Strangely the extension seemed to start it on its own:

The Task "SuperBOL: build (debug)" could not be found.

I've then added an empty string

				"preLaunchTask": "",

with the result of a seemingly hanging debugger (that should be solved first) and finding the following in the extension host output log:

[error] TypeError: Cannot read properties of undefined (reading 'toString')
	at MI2.<anonymous> (/opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:70:1520)
	at Generator.next (<anonymous>)
	at /opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:1:1994
	at new Promise (<anonymous>)
	at __async (/opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:1:1680)
	at /opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:70:1199
	at new Promise (<anonymous>)
	at MI2.load (/opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:70:1168)
	at GDBDebugSession.launchRequest (/opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:80:5328)
	at GDBDebugSession.dispatchRequest (/opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:58:8330)
	at GDBDebugSession.handleMessage (/opt/bin/codium/extensions/ocamlpro.superbol-0.1.3-linux-x64/_dist/superbol-vscode-platform-bundle.js:52:135700)

which should be fixed as a second part (if it "looks" to hang then only "reload window" helps)
The same happens if I click on "debug anyway" in the first upcoming message.

As a last part I suggest to not try a preLaunch that is not configured - vscode handles the configured ones on its own, and that's the way it should be.

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

No branches or pull requests

2 participants