Lines Matching +full:remote +full:- +full:pid

32 .Cd "makeoptions DEBUG=-g"
43 .Bl -bullet
53 With a firewire link, it can be used to examine the memory of a remote system
56 of use when the remote system has crashed and is no longer responding.
59 When used for remote debugging,
71 .Pq Cd "makeoptions DEBUG=-g" .
86 .Dl "gdb -k -wcore kernel.debug /dev/mem"
108 .Dl "gdb -k kernel.debug /var/crash/vmcore.29"
111 .Ss "Debugging a live system with a remote link"
115 .Dq "remote system"
118 To debug a live system with a remote link, the kernel must be compiled with the
126 .Ss "Debugging a live system with a remote serial link"
127 When using a serial port for the remote link on the i386 platform, the serial
138 .Ss "Debugging a live system with a remote firewire link"
144 .Bl -bullet
148 support, and that the kernel of the remote system includes the
157 On the remote system only:
158 .Bd -literal -offset indent
165 output of the remote system:
166 .Bd -literal -offset indent
195 to find the firewire node corresponding to the remote machine.
197 .Bd -literal -offset indent
205 The first node is always the local system, so in this case, node 0 is the remote
208 corresponds to the remote system.
209 On the remote machine, it looks like this:
210 .Bd -literal -offset indent
221 .Dl "dconschat -br -G 5556 -t 0x000199000003622b"
224 is the EUI64 address of the remote node, as determined from the output of
231 to the remote debugger.
244 It displays error messages and console output for the remote system, so it is a
248 .Bd -literal -offset indent
252 Ready to go.  Enter 'tr' to connect to the remote target
254 or 'trf portno' to connect to the remote target with the firewire
277 .Dl "dconschat -br -G 4711 -t 0x000199000003622b"
280 .Bd -literal -offset indent
285 .Ss "Non-cooperative debugging a live system with a remote firewire link"
287 section, it is possible to debug a remote system without its cooperation, once
298 to the upper and lower halves of the EUI64 ID of the remote system,
300 From the previous example, the remote machine shows:
301 .Bd -literal -offset indent
310 .Bd -literal -offset indent
311 # sysctl -w hw.firewire.fwmem.eui64_hi=0x00019900
312 hw.firewire.fwmem.eui64_hi: 0 -> 104704
313 # sysctl -w hw.firewire.fwmem.eui64_lo=0x0003622b
314 hw.firewire.fwmem.eui64_lo: 0 -> 221739
318 After this, you can examine the remote machine's state with the following input:
319 .Bd -literal -offset indent
320 # gdb -k kernel.debug /dev/fwmem0.0
332 The remote system continues to run.
345 .Bl -tag -width indent
349 This command is only meaningful when performing remote debugging.
357 It is necessary for remote debugging and crash dumps; for local memory debugging
364 remote debugging and crash dumps; use
368 Debug a remote system via the specified serial or firewire interface.
370 Debug a remote system via serial interface
373 Debug a remote system via serial interface
376 Debug a remote system via firewire interface at default port 5556.
390 .Bl -tag -width indent
392 Select stack frame 0 and show assembler-level details.
394 Select stack frame 1 and show assembler-level details.
396 Select stack frame 2 and show assembler-level details.
398 Select stack frame 3 and show assembler-level details.
400 Select stack frame 4 and show assembler-level details.
402 Select stack frame 5 and show assembler-level details.
442 .Bl -tag -width indent
443 .It Ic btp Ar pid
445 .Ar pid .
455 .It Ic defproc Ar pid
456 Specify the PID of the process for some other commands in this section.
473 .Bl -tag -width indent
482 .Va bp->data
505 .Bl -tag -width indent
526 .Bd -literal -offset indent
527 dmesg -M /var/crash/vmcore.0 -N kernel.debug
528 dmesg -M /dev/fwmem0.0 -N kernel.debug
546 .Bd -literal -offset indent
547 ps -M /var/crash/vmcore.0 -N kernel.debug
548 ps -M /dev/fwmem0.0 -N kernel.debug