[lkml]   [1997]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Ugh in 2.1.60
    David Woodhouse wrote:
    > Isn't it a bit difficult to get "file and line number" information?
    > Personally, I liked the approach that I saw in a recent 2.1 kernel:
    > if (code has done somthing wrong)
    > *(int *)0=0;
    > I've forgotten where it was now, but it definitely made sure the offending
    > code was fixed :)

    The copy_xx_user functions are actually macros, so you can have the
    compiler embed the source file name and line (__FILE__, __LINE__, I

    In this case generating an oops would be too draconian -- the code works
    _most_ of the time, we just want to find it and make it 100%.


     \ /
      Last update: 2005-03-22 13:40    [W:0.017 / U:89.128 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site