Searched refs:reap (Results 1 – 11 of 11) sorted by relevance
120 link->next=vb->reap; in _vorbis_block_alloc()122 vb->reap=link; in _vorbis_block_alloc()139 struct alloc_chain *reap=vb->reap; in _vorbis_block_ripcord() local140 while(reap){ in _vorbis_block_ripcord()141 struct alloc_chain *next=reap->next; in _vorbis_block_ripcord()142 _ogg_free(reap->ptr); in _vorbis_block_ripcord()143 memset(reap,0,sizeof(*reap)); in _vorbis_block_ripcord()144 _ogg_free(reap); in _vorbis_block_ripcord()145 reap=next; in _vorbis_block_ripcord()156 vb->reap=NULL; in _vorbis_block_ripcord()
20 Your backend must also provide an event handling function to "reap" ongoing37 platform, you can emulate this using an internal library thread to reap I/O as
110 struct alloc_chain *reap; member
446 * run-native-test.sh: Do kill -9 and reap explicitly at end, since
938 …A9QrealA realisation )J!AD'Q=0'F realization )J!AD'Q=0'Freally#J!AD+reap0rearAreasone…
1030 install a SIGCHLD handler to reap expiried child process; ok markus@
2313 Handle EINTR returns from wait() correctly and reap
4706 V "reap" :G2P
5221 V "reap" :G2P
3347 process has zombies it can reap. On the way out, if we reaped