1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

des         2004/05/18 23:40:52 PDT

  FreeBSD src repository

  Modified files:        (Branch: RELENG_4_7)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_4_8)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_4_9)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_5_0)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_5_1)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_5_2)
    .                    UPDATING 
  Modified files:        (Branch: RELENG_4_7)
    sys/conf             newvers.sh 
  Log:
  Bump and document patch level.
  
  Approved by:    so
  
  Revision        Changes    Path
  1.73.2.74.2.31  +3 -0      src/UPDATING
  1.73.2.80.2.24  +3 -0      src/UPDATING
  1.73.2.89.2.9   +3 -0      src/UPDATING
  1.229.2.27      +3 -0      src/UPDATING
  1.251.2.19      +3 -0      src/UPDATING
  1.282.2.15      +3 -0      src/UPDATING
  1.44.2.26.2.29  +1 -1      src/sys/conf/newvers.sh

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

    You can actually run gdb on a live kernel like this:

    gdb -k /dev/mem /path/to/kernel.debug

    You can then use the 'proc' command to switch to a process (give it a
    pid), and do a stack backtrace.  That part only really works if the
    process is blocked on something (i.e. not running).

    But you can also dig around kernel globals and various data structures
    and that can be quite useful on a live system.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>