From owner-freebsd-questions Mon Jul 15 11:38:29 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 720DC37B400 for ; Mon, 15 Jul 2002 11:38:25 -0700 (PDT) Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 096A643E31 for ; Mon, 15 Jul 2002 11:38:24 -0700 (PDT) (envelope-from fgleiser@cactus.fi.uba.ar) Received: from localhost (localhost [127.0.0.1]) by cactus.fi.uba.ar (8.11.6/8.11.6) with ESMTP id g6FIZWf18724; Mon, 15 Jul 2002 15:35:32 -0300 (ART) (envelope-from fgleiser@cactus.fi.uba.ar) Date: Mon, 15 Jul 2002 15:35:32 -0300 (ART) From: Fernando Gleiser X-X-Sender: To: "Balaji, Pavan" Cc: Subject: RE: Unable to compile the kernel In-Reply-To: <3D386AED1B47D411A94300508B11F18703BC5BAE@fmsmsx116.fm.intel.com> Message-ID: <20020715152118.V13499-100000@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 15 Jul 2002, Balaji, Pavan wrote: > > > > Which error? > > No fixed error. I just core dumps at random places. It sounds weird, since > it's only a compilation and not a runtime library, but it's been happening > since last night. gcc dying and dumping core at random places is an indication of harware problems. The most common are: 1. faulty memory 2. faulty cache 3. cooling problems 4. overclocking 5. Bad timing settings in the BIOS If it were related to your new kernel, it would be more deterministic. > > > > > > Which system call? > > My own system call. It's an empty function right now. > How did you add the syscall? Is it a KLD or is it built into the kernel? Did you modify syscalls.master. How did you get the syscall #?. Could you post your syscall code and *any other modifications to the kernel* you made? > > > > Did anyone else have such a problem? Any suggestions? Tips? > > > > Could you post more details? > > I suspect some dumb a** must have hardcoded the number of system calls > somewhere in the kernel and that's what is giving the problem. No, it is not. You can even add syscalls dynamically via a KLD. It is easier to develop the syscall as a KLD and then add it statically to the kernel. Fer > > > Pavan Balaji, > CIS Graduate Student, > Ohio State University > > "Being happy doesn't mean that everything is perfect... It just means that > you have decided to see beyond the imperfections" -- Rash > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message