On Sun, 4 Oct 2015, Paul Goyette wrote:
| 1. Is it correct for init's p_nstopchild to be zero when it has several
| children whose p_state is SSTOP?
Depends whether those children have previously been waited for or not.
Stopped children don't go away when they're waited for, so there need
In attempts to debug another problem (see the thread about "killing
zombies"), I've twice forced crash dumps from ddb. Once with the 'sync'
command, and once with 'reboot 0x104'.
Both crash dump files appear valid
# file netbsd.4.core
netbsd.4.core: NetBSD kernel core file, amd64 BSD, (header
On Sun, 4 Oct 2015, Robert Elz wrote:
Date:Fri, 2 Oct 2015 15:26:42 +0800 (PHT)
From:Paul Goyette
Message-ID:
| 1. Is it correct for init's p_nstopchild to be zero when it has several
| children whose p_state is SSTOP?
Depends whether those children have previ
Date:Fri, 2 Oct 2015 15:26:42 +0800 (PHT)
From:Paul Goyette
Message-ID:
| 1. Is it correct for init's p_nstopchild to be zero when it has several
| children whose p_state is SSTOP?
Depends whether those children have previously been waited for or not.
Stoppe
Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/debug/ad.arm
P src/doc/CHANGES
P src/external/cddl/osnet/dev/dtrace/arm/dtrace_isa.c
P src/external/cddl/osnet/dev/sdt/sdt.c
P src/external/cddl/osnet/dist/uts/common/sys/dtrace.h
P src/external/cddl/osnet/sys/sys/sdt.h
P
