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 [EMAIL PROTECTED] Millions Consulting Limited To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
