Heh -- letting old vectors leak may still not be good enough. Martin posted the relevant code: ((I) < narenas && (uptr)(P) - arenas[I] < (uptr)ARENA_SIZE) The problem remaining is that narenas can get out of synch with arenas, and if narenas refers to a later arena size, arenas[I] may be an out-of-bounds reference. This may be a good reason to make "narenas" and "arenas" volatile, in order to ensure that the former is read up before the latter.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4