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

Debugging Not Working After Upgrade to 1.1.37 #15439

Closed
k3341095 opened this issue Nov 27, 2024 · 2 comments · Fixed by #15788
Closed

Debugging Not Working After Upgrade to 1.1.37 #15439

k3341095 opened this issue Nov 27, 2024 · 2 comments · Fixed by #15788
Assignees
Labels
bug Something isn't working confirmed bug We can reproduce this issue

Comments

@k3341095
Copy link

What version of Bun is running?

1.1.37+8ca0eb831

What platform is your computer?

Linux 6.8.0-49-generic x86_64 x86_64

What steps can reproduce the bug?

console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");
console.log("Hello via Bun!");

Set breakpoints on lines 1 to 4.
Run the debugger.

What is the expected behavior?

The breakpoint only stops at line 1.

What do you see instead?

The breakpoints do not trigger, and the program simply continues running without stopping.

Debugger attached.
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Hello via Bun!
Debugger detached.

Additional information

In version 1.1.36, breakpoints are triggered, but as reported previously, the breakpoint incorrectly stops at line 2 instead of line 1.
After upgrading to 1.1.37, the breakpoints no longer work at all — the program just runs without stopping.
The expected behavior is for the breakpoint to trigger on line 1.

#15131

@k3341095 k3341095 added bug Something isn't working needs triage labels Nov 27, 2024
@RiskyMH RiskyMH added the confirmed bug We can reproduce this issue label Nov 27, 2024
@LoganTann
Copy link

I'm experiencing the same issue. Downgraded to 1.1.36, I can confirm this issue happens only on 1.1.37.

@devtrader
Copy link

devtrader commented Dec 4, 2024

Experiencing the same not hitting breakpoints issue. Solved by downgrading Bun to 1.1.36 as suggested above. Unlike above no breakpoints were hit at all, not even line 1.

Visual Studio Code v1.95.3
Bun for Visual Studio Code v0.0.25
Typescript v5.7.2

bun v1.1.38 - Breakpoints not hit in VSCode
bun v1.1.37 - Breakpoints not hit in VSCode
bun v1.1.36 - Works.
bun v1.1.35 - Works

VSCode configuration
{
"name": "Bun File",
"program": "${file}",
"cwd": "${workspaceFolder}",
"request": "launch",
"type": "bun",
},

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed bug We can reproduce this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants