Pftop broken in pfSense 2.0.3?

[wallabybob]

A few weeks ago I upgraded from 2.0.1 to 2.0.3 (reported as

2.0.3-RELEASE (i386)
built on Fri Apr 12 10:22:57 EDT 2013
FreeBSD 8.1-RELEASE-p6

). pftop now produces a garbled display, for example:
[2.0.3-RELEASE][root@pfsense.example.org]/root(1): pftop

pfTop: Up State 1-19/50, View: default, Order: none, Cache: 10000      21:15:21

PR    D SRC                  DEST                STATE  AGE  EXP  PKTS BYTES
icmp  I 192.168.37.200:0      192.168.37.197:32515  0:0  3721m    10  436K  35M
ipcom I (null)[0]            (null)[0]            0:0  3722m    0  538K    *
ip    I (null)[6264]          (null)[0]            0:0      0    *  856K    *
ip    I (null)[0]            (null)[49320]        255:6 2358d    *    *    *
leaf- I (null)[10417]        (null)[0]            0:4      *    0    *    *
carp  I (null)[0]            (null)[60080]        0:0      0    0    *    *
larp  I (null)[61558]        (null)[1]            0:0  57603    *    * 3202M
leaf- I (null)[0]            (null)[0]            0:255    0    0    *    *
iatp  I (null)[39000]        (null)[0]            0:0      0 57603 3202M    *
cphb  I (null)[22570]        (null)[0]            0:0      *    0    *    *
igmp  I (null)[0]            (null)[0]            0:0      0    0    *    *
ip    I (null)[0]            (null)[57421]        0:0  57603 2210m    * 3202M
ip    I (null)[0]            (null)[0]            1:0  2184m 1973h    *    *
155  I (null)[33013]        (null)[24654]        0:0      0    * 1610M    *
ip    I (null)[0]            (null)[40501]        206:0    0    *    *    *
ip    I (null)[0]            (null)[0]            203:0    0    *    *    *
ip    I (null)[0]            (null)[0]            0:1      0    *    *    *
255  I (null)[65535]        (null)[0]            0:0      0    *    *    *
[2.0.3-RELEASE][root@pfsense.example.org]/root(2): 237:2    1    *    *

Here's a pftop run in pfSense 2.1-RC0 showing the sort of display I expect to see on pfSense 2.0.3:
[2.1-RC0][root@pfsense2.test.example.org]/root(1): pftop

pfTop: Up State 1-6/6, View: default, Order: none, Cache: 10000        21:13:57

PR    D SRC                  DEST                STATE  AGE  EXP  PKTS BYTES
icmp  O 192.168.211.217:18061 192.168.211.173:0    0:0    268    9  534 34176
udp  I 192.168.211.241:17500 255.255.255.255:1750  0:1    267    4    9  1260
udp  I 192.168.211.241:17500 192.168.211.255:1750  0:1    267    4    9  1260
tcp  I 192.168.211.241:42436 192.168.211.217:22    4:4    250 86395  190 25264
ipv6- I fe80::230:18ff:feb0:5 ff02::1[16384]        0:0    22    0    2  368
ipv6- O fe80::230:18ff:feb0:5 ff02::1[0]            0:0    22    0    2  368

I noticed pftop seemed to be created more than a year before the kernel:
[2.0.3-RELEASE][root@pfsense.example.org]/root(3): ls -l /boot/kernel/kernel.gz 
-r-xr-xr-x  1 root  wheel  7955924 Apr 13 00:50 /boot/kernel/kernel.gz
[2.0.3-RELEASE][root@pfsense.example.org]/root(4): which pftop
/usr/local/sbin/pftop
[2.0.3-RELEASE][root@pfsense.example.org]/root(5): ls -l /usr/local/sbin/pftop
-r-xr-xr-x  1 root  wheel  100780 Dec 13  2011 /usr/local/sbin/pftop

[2.0.3-RELEASE][root@pfsense.example.org]/root(8): md5  /usr/local/sbin/pftop
MD5 (/usr/local/sbin/pftop) = db03876d70717d447527efdbed32c750

Perhaps pftop needs to know the details of some kernel data structures and was built with (now) stale definitions.