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

Jump to bottom

Cycle-count display is a junk format string (Windows) #1817

Closed
RetroEdit opened this issue Jul 11, 2020 · 1 comment
Closed

Cycle-count display is a junk format string (Windows) #1817

RetroEdit opened this issue Jul 11, 2020 · 1 comment

Comments

@RetroEdit
Copy link

@RetroEdit RetroEdit commented Jul 11, 2020 •
edited

I happened to open up a recent mGBA (specifically, 0.9-6257-cdf9105f56182a207662c93da1e7a3a7f6bb2040) for some testing. I noticed cycle count had been added to the debugger. However, it just displays as %I64u on Windows.

This looks like a similar type of issue as #1794.
@endrift
Copy link
Member

@endrift endrift commented Jul 11, 2020

That shouldn't be possible...I don't use that format string anymore. I wonder what's going on.

endrift added a commit that referenced this issue Jul 11, 2020
@endrift
All: Correct more format strings on Windows (fixes #1817)
Loading status checks…
8e3be05
@endrift endrift closed this in 73c38b9 Jul 11, 2020
RetroEdit added a commit to TASVideos/mgba that referenced this issue Aug 29, 2020
@endrift @RetroEdit
All: Correct more format strings on Windows (fixes mgba-emu#1817)
Verified
This commit was signed with the committer’s verified signature.
RetroEdit
GPG key ID: CE9E2A36E1EFA76F Learn about vigilant mode.
60a01dd
vadosnaprimer added a commit to TASVideos/mgba that referenced this issue Aug 30, 2020
@endrift @vadosnaprimer
All: Correct more format strings on Windows (fixes mgba-emu#1817)
1ba5f5e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@endrift @RetroEdit