From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 25 14:37:09 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 967BB16A41F for ; Sun, 25 Dec 2005 14:37:09 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: from web35708.mail.mud.yahoo.com (web35708.mail.mud.yahoo.com [66.163.179.162]) by mx1.FreeBSD.org (Postfix) with SMTP id 1964343D49 for ; Sun, 25 Dec 2005 14:37:09 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: (qmail 29775 invoked by uid 60001); 25 Dec 2005 14:37:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=KlnAwyWN2ebhJR6ahx7m0BjAAN+acQ1UZjDi2wpAM59rrZxIgt6F1TK0lYoWUJSEUaPU00IXE5tdef1NKwoA4G8//ncIKZTqyDHvMkrd5mYFyI3PY8d89vwlpPg9KpuTI4XJgjspLPeMOstQau4fNUtgqNMu2XEAY6byooy8k8o= ; Message-ID: <20051225143708.29773.qmail@web35708.mail.mud.yahoo.com> Received: from [202.79.62.27] by web35708.mail.mud.yahoo.com via HTTP; Sun, 25 Dec 2005 06:37:08 PST Date: Sun, 25 Dec 2005 06:37:08 -0800 (PST) From: kamal kc To: delphij@delphij.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2005 14:37:09 -0000 thanks, i will try INVARIANTS and WITNESS options and will try to get freebsd 6.0. it will be only tomorrow when i'll be able to do this because it is already evening and i will go to my office tomorrow only. in the mean time if the memory corruption is the problem then is there any option/configuration or possible thing i could do to make sure that the kernel quits or throws some messages or panics on the moment the corruption takes place rather than some time later when other program is affected by it. that way i could locate any bug in my code if present. thanks, kamal Xin LI wrote: Hi, On 12/25/05, kamal kc wrote: [...] > Is the problem related to memory leaks or sleeping > on mutexes or some other causes. >From the backtrace you have provided, it looks like a memory corruption. In order to aid your debugging, you will want INVARIANTS and WITESS, etc. to be enabled. Also, if feasible, please consider using code from -CURRENT or at least RELENG_6_0, as there are more debugging aids that is likely to catch bugs early. Cheers, -- Xin LI http://www.delphij.net _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" --------------------------------- Yahoo! DSL Something to write home about. Just $16.99/mo. or less