Date: Tue, 10 Sep 2002 10:36:37 -0600 From: Stacy Millions <stacy@millions.ca> To: Terry Lambert <tlambert2@mindspring.com>, hackers@FreeBSD.org Subject: Re: I climb the mountain seeking wisdom Message-ID: <3D7E1F95.4070605@millions.ca> References: <XFMail.20020906135858.jhb@FreeBSD.org> <3D78F291.8010005@millions.ca> <20020908064449.GG46846@wantadilla.lemis.com> <3D7D212E.6030601@millions.ca> <20020910021732.GB20691@wantadilla.lemis.com> <3D7D639A.99E034EC@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D7E1F95.4070605>