Doesn't matter how many times it's been read, it's always ready to be read again. I haven't checked yet to see if this might have something to do with a deleted/purged message being near the scan_ptr set yet; I think I need to code in some more debugging info. The challenge at this point is how to do that without adding to the giant clusterfuck that is becoming the debug output already; another custom debugging flag, no doubt.
If this doesn't have anything to do with a deleted/purged message slot, there is something fundamentally wrong with the algorithm in readNew(). End of transmission.
dgets
commented
8 years ago
Doesn't matter how many times it's been read, it's always ready to be read again. I haven't checked yet to see if this might have something to do with a deleted/purged message being near the
scan_ptrset yet; I think I need to code in some more debugging info. The challenge at this point is how to do that without adding to the giant clusterfuck that is becoming the debug output already; another custom debugging flag, no doubt.If this doesn't have anything to do with a deleted/purged message slot, there is something fundamentally wrong with the algorithm in
readNew(). End of transmission.