Date: Thu, 29 Jun 2000 12:38:15 -0400 (EDT) From: David Gilbert <dgilbert@velocet.ca> To: Alfred Perlstein <bright@wintelcom.net> Cc: David Gilbert <dgilbert@velocet.ca>, Freebsd-stable@FreeBSD.ORG Subject: Re: dc19 fructration. Message-ID: <14683.31607.612798.996185@trooper.velocet.net> In-Reply-To: <20000629090749.J275@fw.wintelcom.net> References: <14683.24171.98558.24798@trooper.velocet.net> <20000629090749.J275@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Alfred" == Alfred Perlstein <bright@wintelcom.net> writes: Alfred> Using truss or gdb on ifconfig may help you find out which Alfred> syscall is the culpret. Problem is that the system crashes before ifconfig -a completes, and it would appear that the stack smashing that whatever syscall is running does will bring down the kernel regardless of how I proceed. I was asking specifically if someone new the approximate code path that ifconfig -a traversed since I was having trouble collecting this data. I would assume that even if I knew what syscall was running that I'd have to trace my way through a maze of function pointers before I got my way clear. dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14683.31607.612798.996185>