Searched refs:arenaindex (Results 1 - 1 of 1) sorted by relevance

/third_party/python/Objects/
H A D	obmalloc.c	913 * size, then `POOL_ADDR(p)->arenaindex' could rarely cause a segmentation 1007 uint arenaindex; /* index into arenas of base adr */ member 1703 arenas[(POOL)->arenaindex].address. Then P belongs to the arena if and only if 1716 (POOL)->arenaindex < maxarenas must be false, saving us from trying to index 1720 arenas[(POOL)->arenaindex]. Suppose obmalloc controls P. Then (barring wild 1728 call to the system malloc() or realloc()). (POOL)->arenaindex may be anything 1729 in this case -- it may even be uninitialized trash. If the trash arenaindex 1733 Else arenaindex is < maxarena, and AO is read up. If AO corresponds to an 1753 2.5, arenas were never free()'ed, and an arenaindex < maxarena always 1759 memory when P is not controlled by obmalloc (to get at (POOL)->arenaindex) 1777 uint arenaindex = *((volatile uint *)&pool->arenaindex); address_in_range() local [all...]

Completed in 3 milliseconds

Indexes created Thu Nov 07 10:32:03 CST 2024