From owner-freebsd-hackers Tue Sep 10 9:36:49 2002 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 D09CE37B400 for ; Tue, 10 Sep 2002 09:36:46 -0700 (PDT) Received: from Millions.Ca (h24-79-52-254.sbm.shawcable.net [24.79.52.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2176B43E4A for ; Tue, 10 Sep 2002 09:36:46 -0700 (PDT) (envelope-from stacy@Millions.Ca) Received: (from uucp@localhost) by Millions.Ca (8.11.1/8.9.3) id g8AGajw69200; Tue, 10 Sep 2002 10:36:45 -0600 (MDT) (envelope-from stacy@Millions.Ca) Received: from Cedar.Millions.Ca(192.168.64.8) via SMTP by mail-gw-0.millions.ca, id smtpdU69198; Tue Sep 10 10:36:38 2002 Received: from millions.ca (Bonsai.Millions.Ca [192.168.64.4]) by cedar.millions.ca (8.12.2/8.12.3) with ESMTP id g8AGabcM097704; Tue, 10 Sep 2002 10:36:38 -0600 (MDT) (envelope-from stacy@millions.ca) Message-ID: <3D7E1F95.4070605@millions.ca> Date: Tue, 10 Sep 2002 10:36:37 -0600 From: Stacy Millions Organization: Millions Consulting Limited User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert , hackers@FreeBSD.org Subject: Re: I climb the mountain seeking wisdom References: <3D78F291.8010005@millions.ca> <20020908064449.GG46846@wantadilla.lemis.com> <3D7D212E.6030601@millions.ca> <20020910021732.GB20691@wantadilla.lemis.com> <3D7D639A.99E034EC@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > Greg 'groggy' Lehey wrote: > >>There will always be situations where the debugger can't catch the >>problem in time. Then it's up to you to guess and put a breakpoint >>just before it freezes; this can be an interative process. The method >>requiring the least thought is to single step over function calls >>until the system freezes. Then you know which function it happened >>in. Reboot, set a breakpoint in that function, and repeat. > > > Dumping a bunch of printf's in, with "Here 1\n", "Here 2\n", and so > on will find this problem a lot faster than an equivalent number of > reboots. 8-). A "tried and true" debugging technique, to be sure. Unfortunately, the panic was happening outside of my code (due to something stupid I was doing inside of my code) so putting printfs in my code did not help much. -stacy -- If they keep lowering education standards and raising the price of gasoline, there are going to be a lot of stupid people walking around. Stacy Millions stacy@millions.ca Millions Consulting Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message