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

Emulation starts before debugger has settled #1950

Closed
felixjones opened this issue Nov 24, 2020 · 2 comments
Closed

Emulation starts before debugger has settled #1950

felixjones opened this issue Nov 24, 2020 · 2 comments

Comments

@felixjones
Copy link

@felixjones felixjones commented Nov 24, 2020

8:10 in my video shows this: https://youtu.be/ZFRWBSMC5eI?t=490

At the moment this means I have to add an artificial delay at the start of the program to wait for everything to settle before my breakpoints work. This also means I can't place a reliable breakpoint at the very start of the program, at the entry point.

This happens with CLion, VSCode and Visual Studio.

@endrift
Copy link
Member

@endrift endrift commented Nov 24, 2020

Yeah, this is a problem with the core starting on a second thread, and program flow on the main thread doesn't get to the debugger on the main thread until the CPU thread has had a little time to spin. I'll see if I can add a way to block startup when needed.

@endrift endrift closed this in 42879af Nov 25, 2020
@endrift
Copy link
Member

@endrift endrift commented Nov 25, 2020

This ended up being easier than I thought. Whoops.

endrift added a commit that referenced this issue Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants