[Neal Norwitz]
> This is good news. I changed ADDRESS_IN_RANGE to a function,
> then suppressed it. There were no other uninitialized memory reads.
Cool! In
if (ADDRESS_IN_RANGE(p, pool->arenaindex)) {
it's actually only the pool->arenaindex subexpression that may read
uninitialized memory; the ADDRESS_IN_RANGE macro itself doesn't do anything
"bad".
> Valgrind does report a bunch of problems with pthreads, but
> these are likely valgrind's fault. There are some complaints
> about memory leaks, but these seem to appear only to occur
> when spawning/threading. The leaks are small and short lived.
A novel definition for "leak" <wink>.
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