More debugging in search of wtf for issue #140#159
Merged
Conversation
dgets
added a commit
that referenced
this pull request
May 31, 2015
More debugging in search of wtf for issue #140; turns out the whole thing was just Ddoctest's message pointers being corrupted.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After some more in-depth debugging (still there, but mostly commented out) about why the negative message scan numbers are being hit and forward scan isn't working, but only for Ddoctest, I believe that I've found it's due to something having corrupted the pointers for that particular user. None of the other users have it, even if they switch to Ddoc and login the same way. Code that I know was ironclad back in the day has the bug, it's got to be a corrupted last message pointer for Ddoctest. So now I need to go about figuring how to fix that; good news is that the code isn't borked.