Searched refs:handle (Results 1 – 7 of 7) sorted by relevance
29 gattc_write_char_by_instance_id [handle] [size]37 gattc_write_invalid_char_by_instance_id [handle] [size]203 gattc_read_char_by_instance_id [handle]208 gattc_read_invalid_char_by_instance_id [handle]214 gattc_mod_read_char_by_instance_id [handle]220 gattc_mod_read_char_by_instance_id [handle]227 gattc_mod_read_char_by_instance_id [handle]241 gattc_mod_read_char_by_instance_id [handle]278 gattc_mod_read_char_by_instance_id [handle]280 gattc_mod_read_char_by_instance_id [handle][all …]
57 Save handle from create mdep79 Save handle from create mdep287 Save handle from create mdep303 Save handle from create mdep
37 To handle pointer offset, for eg, (gdb) print_ptr malloc_ptr + 339 To handle custom allacator, may be watch_heap command could take in arguements
864 handle(node.returnType, node.uAnnotations) in <lambda>()872 handle(type.type, psiAnnotations = type.annotations) in <lambda>()880 handle(node.type, node.uAnnotations) in <lambda>()884 private fun handle( in <lambda>() method
71 // in the FileDescriptorProtos and handle them one by one rather than read
113 Some variables are available to make it easier to handle OS differences. These
META-INF/ META-INF/MANIFEST.MF META-INF/maven/ META- ...