On Tue, Dec 23, 2008 at 11:27 AM, Ryan Graham <[email protected]> wrote: > On Tue, Dec 23, 2008 at 11:18 AM, Chris Miller > <[email protected]> wrote: >> >> On Tue, Dec 23, 2008 at 11:14 AM, Ryan Graham <[email protected]> wrote: >>> On Tue, Dec 23, 2008 at 11:03 AM, Chris Miller >>> <[email protected]> wrote: >>>> You can build a debug version of your kernel. It's not hard. >>> >>> Easy != useful >>> >>> The OP said "basic C and C++ programs to get familiar with using the >>> debugger". I'm pretty sure debugging the kernel is a little out of >>> scope. >> >> The kernel is just C code. It's not that difficult to get around. >> Well, some people would disagree... >> > > again, easy != useful > > Tracing kernel code because you forgot to initialize a pointer before > your NULL check is a waste of time. Sure, you could trace it down to > where the actual page fault is, but that's not going to help you > realize your mistake any faster; indeed it will only slow you down > more. Debugging the kernel when your code doesn't behave is a last > resort.
Well, debugging the kernel is kinda stupid too.... so few bugs there it's more or less pointless. -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman | John 3:16! http://www.fsdev.net/ | http://lordsauron.wordpress.com/ Parents, Take Responsibility For Your Kids! http://www.whattheyplay.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
