Messages in this thread | | | Date | Fri, 31 Oct 1997 10:44:41 -0500 | From | Bill Hawes <> | Subject | Re: 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 think.)
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%.
Regards, Bill
| |