Searched refs:resumed (Results 1 – 18 of 18) sorted by relevance
385 lp->resumed = 1; in lin_lwp_attach()498 lp->resumed = 0; in resume_clear_callback()505 lp->resumed = 1; in resume_set_callback()537 lp->resumed = 1; in lin_lwp_resume()925 return (lp->status != 0 && lp->resumed); in status_callback()933 return (lp->stopped == 0 || (lp->status != 0 && lp->resumed)); in running_callback()1081 return lp->resumed; in resumed_callback()1288 gdb_assert (lp->resumed); in lin_lwp_wait()1478 gdb_assert (lp->resumed); in lin_lwp_wait()
55 /usr/bin/logger -t $subsystem resumed at `/bin/date +'%Y%m%d %H:%M:%S'`
6 reported were not related to ncurses. After that, I resumed development,
448 BOOL resumed; in start_blocking_thread_internal() local470 resumed = ResumeThread(c->thr_table[0].thnd); in start_blocking_thread_internal()471 DEBUG_INSIST(resumed); in start_blocking_thread_internal()
172 int32_t (*resumed)( VCHI_MDRIVER_HANDLE_T *handle ); member
46 over the sessions that can be resumed if desired.
112 resumed session the applications will have all this state information available
45 - * non-zero session length would never reach here) it cannot be a resumed49 + /* If we have no ticket it cannot be a resumed session. */
44 - * resumed session.47 + /* If we have no ticket it cannot be a resumed session. */
287 * @param dev the device being resumed
2331 time as the program is about to be resumed, GDB might not be able to2333 be printed only when the program is resumed:3286 current thread may run when the inferior is resumed. The `step'
654 account of a signal and would ordinary see the signal when resumed1743 target is generally not resumed. It will wait for GDB (this
2787 time as the program is about to be resumed, @value{GDBN} might not be2789 warning will be printed only when the program is resumed:3890 current thread may run when the inferior is resumed. The @code{step}9642 a signal and would ordinary see the signal when resumed with the10870 the target is generally not resumed. It will wait for @value{GDBN}
385 resumed.) Note that x86 debug registers are used both for hardware
914 *) If a multithreaded client connects to a malicious server using a resumed1579 overrun vulnerability: resumed sessions must not be modified as they can1608 compression algorithm of the resumed session instead of determining
1684 resumed that then fails and sends an error message. (Thanks to
2561 * fix datastream corruption during resumed transfer in ra_serf (r1154733)
68246 twice-resumed