From owner-freebsd-hackers Thu Apr 1 10:54:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from silver.teardrop.net (silver.teardrop.net [216.155.28.66]) by hub.freebsd.org (Postfix) with ESMTP id 8115D15D46 for ; Thu, 1 Apr 1999 10:54:30 -0800 (PST) (envelope-from sno@teardrop.org) Received: from localhost (sno@localhost) by silver.teardrop.net (8.9.2/8.9.2) with ESMTP id NAA41142 for ; Thu, 1 Apr 1999 13:57:01 -0500 (EST) (envelope-from sno@teardrop.org) Date: Thu, 1 Apr 1999 13:57:01 -0500 (EST) From: James Snow X-Sender: sno@silver.teardrop.net To: freebsd-hackers@freebsd.org Subject: That Array Thing 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 Just to quickly and generically reply to everyone who wrote to me about my curiosity and my array: Apologies if it wasn't the correct list, but my question wasn't really about C, it was more about how the FreeBSD kernel does stuff with a process and how that process is laid out in memory. What gets overwritten, why did the process start sucking up swap, etc. All in all though, your replies answered my question and cleared up some of my understanding of kernel process management. And yes, I know that no C program would be written like that. That's why I wrote it that way. :) Thanks and sorry for the noise. -sno o - - - - - - - - - - - - - o - - - - - - - - - - - - o | We live in the short term | sno at teardrop dot org | | and hope for the best. | I am Geek. Hear me ^G | o - - - - - - - - - - - - - o - - - - - - - - - - - - o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message