Lines Matching full:stub
5695 targets, this functionality may further depend on the remote stub's
6367 remote stub; however, none of the stubs distributed with GDB support
6672 snapshot. When the remote stub is focused on a trace snapshot, it will
10319 `stub type has NULL name'
10473 if you have some other way of getting the stub to the target
10611 * remote stub:: Implementing a remote stub
10707 will depend on your particular remote stub. After the `detach'
10732 without linking in the usual debugging stub.
10824 File: gdb.info, Node: Remote configuration, Next: remote stub, Prev: Server, Up: Remote Debugging
10904 debugging stub. If you need to override the autodetection, you can use
10912 If you do, that may be a bug in your remote debugging stub, or a bug in
10937 File: gdb.info, Node: remote stub, Prev: Remote configuration, Up: Remote Debugging
10939 17.4 Implementing a remote stub
10942 The stub files provided with GDB implement the target side of the
10946 implementing your own stub file, you can still ignore the details: start
10947 with one of the existing stub files. `sparc-stub.c' is the best
10980 containing these subroutines is called a "debugging stub".
10983 `gdbserver' instead of linking a stub into your program. *Note
10986 The debugging stub is specific to the architecture of the remote
10987 machine; for example, use `sparc-stub.c' to debug programs on SPARC
10992 `i386-stub.c'
10995 `m68k-stub.c'
10998 `sh-stub.c'
11001 `sparc-stub.c'
11004 `sparcl-stub.c'
11013 * Stub Contents:: What the stub can do for you
11014 * Bootstrapping:: What you must do for the stub
11018 File: gdb.info, Node: Stub Contents, Next: Bootstrapping, Up: remote stub
11020 17.4.1 What the stub can do for you
11023 The debugging stub for your architecture supplies these three
11064 File: gdb.info, Node: Bootstrapping, Next: Debug Session, Prev: Stub Contents, Up: remote stub
11066 17.4.2 What you must do for the stub
11073 First of all you need to tell the stub how to communicate with the
11094 probably requires changes to the standard stub; one quick and dirty way
11102 handling tables. You need to do this because the stub does not
11139 library subroutines as well; this varies from one stub to another, but
11144 File: gdb.info, Node: Debug Session, Prev: Bootstrapping, Up: remote stub
11153 (*note What you must do for the stub: Bootstrapping.):
11162 3. For the 680x0 stub only, you need to provide a variable called
11173 4. Compile and link together: your program, the GDB debugging stub for
13053 Tell GDB whether to add this host to the remote stub's arguments
13057 Show whether to add this host to remote stub's arguments when
21017 The host (GDB) sends COMMANDs, and the target (the debugging stub
21045 must always be escaped. Responses sent by the stub must also escape
21064 For any COMMAND not supported by the stub, an empty response
21069 A stub is required to support the `g', `G', `m', `M', `c', and `s'
21135 send some kind of out-of-band message to a specially-setup stub
21240 The stub need not use any particular size or alignment when
21242 word-aligned and LENGTH is a multiple of the word size, the stub
21382 Direct the stub to erase LENGTH bytes of flash starting at ADDR.
21388 stub is allowed to delay erase operation until the `vFlashDone'
21399 Direct the stub to write data to flash address ADDR. The data is
21421 Indicate to the stub that flash programming operation is finished.
21422 The stub is permitted to delay or batch the effects of a group of
21626 the stub.
21631 stub. These packet names follow some conventions:
21732 by the stub.
21799 Tell the remote stub about features supported by GDB, and query
21800 the stub for features it supports. This packet allows GDB and the
21801 remote stub to take advantage of each others' features.
21816 The stub supports or does not support each returned
21845 Whenever the stub receives a `qSupported' request, the supplied
21847 allows GDB to put the stub in a known state, even if the stub had
21855 future to let the stub take advantage of new features in GDB, e.g.
21858 were not implied by the `qSupported' query. The stub's reply
21860 GDB describes all the features it supports, and then the stub
21863 Similarly, GDB will silently ignore unrecognized stub feature
21866 Some features are flags. A stub which supports a flag feature
21868 values, and the stub should respond with an `=' form response.
21873 stub is free to omit any feature responses that match the defaults.
21876 probing mechanism is useful: in some cases, a stub's internal
21882 These are the currently defined stub features and their properties:
21890 These are the currently defined stub features, in more detail:
21893 The remote stub can accept packets up to at least BYTES in
21898 remote protocol packet; if the stub stores packets in a
21900 buffer for the NUL. If this stub feature is not supported,
21904 The remote stub understands the `qXfer:auxv:read' packet
21985 This packet is not probed by default; the remote stub must
21994 This packet is not probed by default; the remote stub must
22024 by the stub, or that the object does not support reading.
22052 by the stub, or that the object does not support writing.
22055 Requests of this form may be added in the future. When a stub does
22057 not recognize the OPERATION keyword, the stub must respond with an
22181 A successful reply from the stub indicates that the stub has found
22226 Establish the given ranges of memory as "transparent". The stub
22233 was hit, so there's no reason for the stub to refuse to provide
22237 Ask the stub if there is a trace experiment running right now.
22272 implementation defined. If the stub is successful at interrupting the
22344 and values. Both GDB and the target's GDB stub are responsible for
24049 stub relies upon, too.]]
25395 * breakpoint subroutine, remote: Stub Contents. (line 31)
25590 * debugging stub, example: remote stub. (line 6)
25829 * Fujitsu: remote stub. (line 69)
25891 * handle_exception: Stub Contents. (line 15)
25934 * i386: remote stub. (line 57)
25935 * i386-stub.c: remote stub. (line 57)
26040 * Intel: remote stub. (line 57)
26135 * m680x0: remote stub. (line 60)
26136 * m68k-stub.c: remote stub. (line 60)
26280 * Motorola 680x0: remote stub. (line 60)
26564 * remote serial debugging, overview: remote stub. (line 14)
26566 * remote serial stub: Stub Contents. (line 6)
26567 * remote serial stub list: remote stub. (line 54)
26568 * remote serial stub, initialization: Stub Contents. (line 10)
26569 * remote serial stub, main routine: Stub Contents. (line 15)
26570 * remote stub, example: remote stub. (line 6)
26571 * remote stub, support routines: Bootstrapping. (line 6)
26581 * Renesas: remote stub. (line 63)
26807 * set_debug_traps: Stub Contents. (line 10)
26810 * SH: remote stub. (line 63)
26811 * sh-stub.c: remote stub. (line 63)
26975 * Sparc: remote stub. (line 66)
26976 * sparc-stub.c: remote stub. (line 66)
26977 * sparcl-stub.c: remote stub. (line 69)
26979 * SparcLite: remote stub. (line 69)
27032 * stub example, remote debugging: remote stub. (line 6)
27486 Node: remote stub440309
27487 Node: Stub Contents443206
