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

Path error when debugger tries to open source file in Codespaces #9

Closed
riestmo opened this issue Jan 18, 2023 · 8 comments
Closed

Path error when debugger tries to open source file in Codespaces #9

riestmo opened this issue Jan 18, 2023 · 8 comments
Assignees

Comments

@riestmo
Copy link

riestmo commented Jan 18, 2023

Type: Bug Report

Describe the bug

  • OS and Version: Ubuntu 20.04
  • VS Code Version: 1.74.3
  • Extension Version: v0.6.2
  • Target Device: CY8C624ABZI-S2D44:Cortex-M4

When starting a debug session in Github Codespaces, the debugger starts successfully and runs to main using the default setting for "debugFrom". However, it fails to open the main.c file as shown below.

image

I suspect it's a similar scheme issue as discussed in #7 (comment)

Expected behavior
The debugger opens the C file once a breakpoint is hit.

@thegecko
Copy link
Contributor

I'll investigate.

Out of interest, are you building the binary in the codespace or somewhere else?

@riestmo
Copy link
Author

riestmo commented Jan 19, 2023

I'm building it in the Codespace.

@thegecko
Copy link
Contributor

This is very frustrating. I think it's a bug in codespaces and github.dev regarding their file schemes.

This used to work, so is a recent regression. I'll need to create a reproducer and file an issue with GitHub

@thegecko
Copy link
Contributor

thegecko commented Jan 20, 2023

@riestmo
Copy link
Author

riestmo commented Jan 23, 2023

Thanks for raising this issue!

@thegecko thegecko self-assigned this Mar 8, 2023
@thegecko
Copy link
Contributor

thegecko commented Apr 3, 2023

@riestmo We've released an update to the debug extension this morning which could fix this issue.

Could you confirm if you see any improvement?

@riestmo
Copy link
Author

riestmo commented Apr 3, 2023

Thanks for the update @thegecko ! I can confirm that the issue is fixed with the latest release v0.9.0.

@riestmo riestmo closed this as completed Apr 3, 2023
@thegecko
Copy link
Contributor

thegecko commented Apr 3, 2023

Nice! Sorry about the delay

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

2 participants