Home | History | Annotate | Download | only in info

Lines Matching full:stubs

6367 remote stub; however, none of the stubs distributed with GDB support
10588 remote stubs--the code that runs on the remote system to communicate
10734 `gdbserver' is not a complete replacement for the debugging stubs,
10990 These working remote stubs are distributed with GDB:
11009 added stubs.
11069 The debugging stubs that come with GDB are set up for a particular chip
11119 The SPARC and 68k stubs are able to mask interrupts themselves
11140 in general the stubs are likely to use any of the common library
21008 output SEQUENCE-IDs. Stubs that handle packets added since GDB 5.0
21644 `,' or `;'. Stubs must be careful to match the full packet name, and
21779 stubs's interpreter may have security implications_.
21806 because it would confuse older clients or stubs. Other features
21851 yet. Stubs should ignore any unknown values for GDBFEATURE. Any
21879 especially common in stubs which may be configured for multiple
22066 `qC' packet has no arguments, but some existing stubs (e.g. RedBoot)
22162 length (400 bytes, for many stubs). There may be only one `R'
22270 Stubs are not required to recognize these interrupt mechanisms and
26551 * remote connection without stubs: Server. (line 6)