On 27-Jan-2003 Morten Rodal wrote:
> On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote:
>> Do you still have the kernel.debug from this kernel lying around?
>> Can you pop gdb up on it and do 'l *0xc01bdb48' please?  That is
>> the instruction pointer from the fault and will give the line that
>> the actual panic occurred at.
>> 
> 
> (kgdb) l *0xc01bdb48
> 0xc01bdb48 is in fork1 (/usr/src/sys/kern/kern_fork.c:388).
> 383                      */
> 384                     p2 = LIST_FIRST(&allproc);
> 385     again:
> 386                     for (; p2 != NULL; p2 = LIST_NEXT(p2, p_list)) {
> 387                             PROC_LOCK(p2);
> 388                             while (p2->p_pid == trypid ||
> 389                                 p2->p_pgrp->pg_id == trypid ||
> 390                                 p2->p_session->s_sid == trypid) {
> 391                                     trypid++;
> 392                                     if (trypid >= pidchecked) {

Well, that's gross.  I have no idea how that could happen.  Somehow
p2 is NULL.  But we shouldn't even be in the loop if p2 is NULL.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to