Home
last modified time | relevance | path

Searched refs:callback (Results 1 – 8 of 8) sorted by relevance

/bionic/libc/netbsd/net/
Dnsdispatch.c100 return (disp_tab[curdisp].callback); in _nsmethod()
/bionic/libc/include/
Dnsswitch.h119 nss_method callback; member
/bionic/libc/private/
Dnsswitch.h119 nss_method callback; member
/bionic/libc/kernel/tools/
Dutils.py231 def walk_source_files(paths,callback,args,excludes=[]): argument
241 walk_source_files([line],callback,args,excludes)
244 callback(path,args)
255 callback( "%s/%s" % (root,f), args )
/bionic/libc/tools/
Dbionic_utils.py348 def walk_source_files(paths,callback,args,excludes=[]): argument
352 callback(path,args)
363 callback( "%s/%s" % (root,f), args )
/bionic/libc/bionic/
Dpthread-timers.c100 thr_timer_func_t callback; member
334 timer->callback = evp->sigev_notify_function; in timer_create()
592 timer->callback(timer->value); in timer_thread_start()
/bionic/libc/kernel/common/linux/mtd/
Dmtd.h51 void (*callback) (struct erase_info *self); member
/bionic/libc/docs/
DOVERVIEW.TXT181 Do not call fork() within a callback provided to pthread_once(). Doing this
185 Also, you can't throw a C++ Exception from the callback (see C++ Exception
363 - If pthread_once() is called with a C++ callback that throws an exception,
368 cleanup handler before the callback to properly unlock the
374 - The same problem may arise if you throw an exception within a callback
376 real-world, but any callback you provide to the C library should *not*