[Neal Norwitz] > ... > I also had problems w/pymalloc originally so I disabled it. > I may try again. There's somthing I found very interesting, though. > > I run purify on a sparc w/gcc 2.95.3 (maybe 3.0.x too, > I can't remember). The problems with pymalloc and some of the dbm > problems were also reported by purify. I've reviewed the code > and can't find any problems. But different tools on different > architectures with somewhat different compilers report similar errors. pymalloc does read uninitialized memory, and routinely, as explained in the msg you're replying to. If that occurs outside code generated for the ADDRESS_IN_RANGE macro, though, it may be a real problem (inside code generated by that macro, reading uninitialized memory is-- curiously enough! --necessary for proper operation).
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