[lkml]   [2002]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [linux-usb-devel] Re: [BK PATCH] USB changes for 2.5.34
    On Mon, 2002-09-16 at 00:24, Larry McVoy wrote:
    > My position is that you either understand the code or you don't. Code
    > that you don't understand is read only. Having a debugger show you some
    > variables isn't going to make you understand the code at the level which
    > is required in order to be making changes.

    It isnt about understanding the code. You issue a perfectly valid
    command to your scsi driver. Your ethernet crashes. All your code is

    Thats a real scenario. In fact thats a horribly common scenario, and the
    kind of thing I have to deal with every day of the week because I debug
    driver code.

    Understanding your own code by using a debugger (or printk) to see what
    is does is not good practice. Understanding misdocumented or crap code
    often needs a debugger to see what is going on, and to be able to
    understand how to fix it. The moment you hit the hardware layer the fun
    really begins, and you need the debugger, not to understand your code
    flow but to snoop around the machine to see what the device did or
    didn't do.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:28    [W:0.022 / U:6.892 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site