Searched refs:telling (Results 1 – 25 of 200) sorted by relevance
12345678
4 # by telling gdbserver (with QPassSignals packet) to pass
676 char telling; member1037 self->seekable = self->telling = r; in textiowrapper_init()1407 if (self->telling) { in textiowrapper_read_chunk()1461 if (self->telling) { in textiowrapper_read_chunk()2205 if (!self->telling) { in textiowrapper_tell()2450 self->telling = self->seekable; in textiowrapper_flush()2498 self->telling = 0; in textiowrapper_iternext()2522 self->telling = self->seekable; in textiowrapper_iternext()
28 In first time you will use rtcBot you will receive a warning telling
38 # telling the layer what types of messages it should report back.
21 RW> twice. There's no telling how libc would react to that.
66 - If it crashes without telling you why, use lots of diagnostic printfs (or
19 short, telling whether to print '``>>>``' or '``...``' next.
193 # create a Trace object, telling it what to ignore, and whether to
195 this. It would be easy to have a rule telling isel to avoid matching MOV32mi
20 We will explain the program after telling you how to compile it.
35 messages telling which features it is checking for.
22 // This is telling us that the result will be available in destination register
32 other info besides telling the user the module is signed since347 with a corrupted index without telling the user
48 messages telling which features it is checking for.
56 messages telling which features it is checking for.
51 some messages telling which features it is checking for.
120 that this seems to be not a well know feature of the policer; Bert was telling
51 messages telling which features it is checking for.
244 ; no way of telling whether they alias. We don't want to use MVC in
245 ; no way of telling whether they alias. We don't want to use NC in
264 PYTHON_EXECUTABLE)`), try telling it explicitly where your Python
56 some messages telling which features it is checking for.