Martin Husemann said:

>And it did complete successfull, without a single core.

I think my build probably will as well, however I'me seeing a problem where
ipmon doesn't put out any data, even when running to stdout. Kernel config
and syslog.conf are okay.

Kdump shows:

 26519 ipmon    EMUL  "netbsd"
 26519 ipmon    RET   nanosleep 0, -268448808/0xefffcbd8
 26519 ipmon    CALL  ioctl(3,FIONREAD,0xefffcc54)
 26519 ipmon    GIO   fd 3 read 4 bytes
       "\0\0\0\0"
 26519 ipmon    RET   ioctl 0, 1074030207/0x4004667f
 26519 ipmon    CALL  nanosleep(0xefffcbe0,0xefffcbd8)
 26519 ipmon    RET   nanosleep 0, -268448808/0xefffcbd8
 26519 ipmon    CALL  ioctl(3,FIONREAD,0xefffcc54)
 26519 ipmon    GIO   fd 3 read 4 bytes
       "\0\0\0\0"
 26519 ipmon    RET   ioctl 0, 1074030207/0x4004667f
 26519 ipmon    CALL  nanosleep(0xefffcbe0,0xefffcbd8)
 26519 ipmon    RET   nanosleep 0, -268448808/0xefffcbd8
 26519 ipmon    CALL  ioctl(3,FIONREAD,0xefffcc54)
 26519 ipmon    GIO   fd 3 read 4 bytes
       "\0\0\0\0"
 26519 ipmon    RET   ioctl 0, 1074030207/0x4004667f
 26519 ipmon    CALL  nanosleep(0xefffcbe0,0xefffcbd8)
 26519 ipmon    RET   nanosleep 0, -268448808/0xefffcbd8
 26519 ipmon    CALL  ioctl(3,FIONREAD,0xefffcc54)
 26519 ipmon    GIO   fd 3 read 4 bytes
       "\0\0\0\0"

Which looks kind of weird compared to another, healthy ipmon kdump.
-- 
Rick Kelly	rmk@rmkhome.com
		<http://www.rmkhome.com/>
		<http://rkba.rmkhome.com/> - the right to keep and bear arms
		<http://wolf.rmkhome.com/> - firearm forums