From owner-freebsd-hackers Sat Jan 30 09:09:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12156 for freebsd-hackers-outgoing; Sat, 30 Jan 1999 09:09:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12151 for ; Sat, 30 Jan 1999 09:09:44 -0800 (PST) (envelope-from howardjp@dragon.ham.muohio.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.9.1/8.9.1) with ESMTP id MAA12145 for ; Sat, 30 Jan 1999 12:26:01 -0500 Date: Sat, 30 Jan 1999 12:26:01 -0500 (EST) From: Jamie Howard To: hackers@FreeBSD.ORG Subject: socketpair(2) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a couple years playing with FreeBSD, having written simple programs, network programs, shared libraries, etc, I figured it was time I tackle my greatest fear: a kernel feature. Since I have need of socketpair(2) supporting PF_INET, it seemed like a logical place to try this out. So I went through the code (as near as I understood it) and got it to find and execute a function called tcp_usr_connect2...this then calls tcp_connect2 (following the "standard"). So my kernel compiles and boots, but when I make a call to socketpair() with PF_INET, it freaks out, displays some debugging information, and reboots. It isn't pretty, to say the least. So the kernel has defeated me. My question is, how can I find out what is going wrong inside there? What should I have and do when I try to modify the kernel? Any suggestions from any other novice kernel hackers out there? Thanks, Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message