Searched refs:examine (Results 1 – 25 of 45) sorted by relevance
12
| /external/zlib/examples/ |
| D | enough.c | 319 local void examine(int syms, int len, int left, int mem, int rem) in examine() function
382 examine(syms - use, len + 1, (left - use) << 1, in examine()
420 examine(n, root + 1, left, 1 << root, 0); in enough()
425 examine((n - left) << 1, root + 1, (n - left) << 1, in enough()
|
| /external/dropbear/ |
| D | queue.h | 46 void *examine(struct Queue* queue);
|
| D | queue.c | 63 void *examine(struct Queue* queue) { in examine() function
|
| D | packet.c | 59 writebuf = (buffer*)examine(&ses.writequeue); in write_packet()
|
| /external/bluetooth/glib/docs/ |
| D | debugging.txt | 9 Such traps lead to immediate code halts to examine the current
|
| /external/iptables/extensions/ |
| D | libip6t_tcp.man | 23 flags which we should examine, written as a comma-separated list, and
|
| D | libipt_tcp.man | 23 flags which we should examine, written as a comma-separated list, and
|
| /external/openssl/crypto/dh/ |
| D | generate | 18 >possible some source code that I could examine.
|
| /external/libvpx/ |
| D | usage_dx.dox | 33 examine the rectangles that describe what data is valid to access and what
|
| D | usage.dox | 39 implementations. Applications \ref MUSTNOT attempt to examine or override
|
| /external/openssl/ |
| D | README.android | 87 e) examine Makefile and compare with ../android-config.mk
|
| /external/e2fsprogs/ |
| D | e2fsprogs.spec | 23 debugfs (used to examine the internal structure of a filesystem, to
|
| D | e2fsprogs.spec.in | 23 debugfs (used to examine the internal structure of a filesystem, to
|
| D | RELEASE-NOTES | 42 ext2fs_dblist_drop_last(), which allows the caller to examine the last
2486 Debugfs can now examine the experimental directory indexing
|
| /external/strace/ |
| D | PORTING | 31 boredom. If the mechanism is neither ptrace nor proc then examine how
|
| /external/chromium/base/ |
| D | mac_util.mm | 48 // This function really does want to examine NSBundle's idea of the main
|
| /external/bluetooth/glib/ |
| D | README.in | 36 only user-visible change is when an application needs to examine an
|
| /external/zlib/doc/ |
| D | rfc1952.txt | 472 values. It must examine FEXTRA/XLEN, FNAME, FCOMMENT and FHCRC
474 present. It need not examine any other part of the header or
|
| /external/bluetooth/glib/docs/reference/glib/ |
| D | running.sgml | 240 Such traps lead to immediate code halts to examine the current program state
|
| /external/qemu/distrib/sdl-1.2.12/src/video/quartz/ |
| D | SDL_QuartzEvents.m | 573 /* If the bit is set, we must always examine it because the left
583 /* If the state changed from pressed to unpressed, we must examine
|
| /external/stlport/doc/ |
| D | FAQ | 203 it should examine both namespace `stlport' and namespace `std' for
|
| /external/dbus/doc/ |
| D | dcop-howto.txt | 202 this method for you. However, until that point you need to examine
|
| /external/jpeg/ |
| D | libjpeg.doc | 1975 many other strategies are possible. For example, the application can examine
2383 into memory, and then examine them at your leisure afterwards.
2413 After jpeg_read_header() completes, you can examine the special markers by
|
| /external/bison/doc/ |
| D | bison.texinfo | 1108 In any semantic action, you can examine @code{yychar} to determine the type of
1111 you can then examine @code{yylval} and @code{yylloc} to determine the
8358 @code{yyparse}.) Error-recovery rule actions may examine this variable.
|
| D | bison.info | 1317 In any semantic action, you can examine `yychar' to determine the
1320 `YYEOF', you can then examine `yylval' and `yylloc' to determine the
7615 `yyparse'.) Error-recovery rule actions may examine this variable.
|
12