Lines Matching full:debugging

59 When used for remote debugging,
68 .Sh PREPARING FOR DEBUGGING
69 When debugging kernels, it is practically essential to have built a kernel with
70 debugging symbols
103 .Ss "Debugging a crash dump"
111 .Ss "Debugging a live system with a remote link"
123 enables the debugging machine stop the debugged machine once a connection has
126 .Ss "Debugging a live system with a remote serial link"
138 .Ss "Debugging a live system with a remote firewire link"
139 As with serial debugging, to debug a live system with a firewire link, the
259 If you are debugging a local system, you can use 'kldsyms' instead
285 .Ss "Non-cooperative debugging a live system with a remote firewire link"
286 In addition to the conventional debugging via firewire described in the previous
289 This corresponds to debugging a local machine using
341 This section discusses only the extensions for kernel debugging that get
343 .Ss "Debugging environment"
344 The following macros manipulate the debugging environment:
349 This command is only meaningful when performing remote debugging.
357 It is necessary for remote debugging and crash dumps; for local memory debugging
362 Read in the symbol tables for the debugging machine.
364 remote debugging and crash dumps; use
523 When debugging a crash dump or over firewire, it is not necessary to start
541 When debugging a crash dump or over firewire, it is not necessary to start
591 Serial debugging is even slower, and race conditions can make it difficult to
595 The debugging macros