Lines Matching full:bug

1 Bug hunting
4 Kernel bug reports often come with a stack dump like the one below::
41 Kernel's source code where the bug happened. Depending on the severity of
44 	BUG: unable to handle kernel NULL pointer dereference at   (null)
51 line is usually required to identify and handle the bug. Along this chapter,
101 Finding the bug's location
104 Reporting a bug works best if you point the location of the bug at the
241 Reporting the bug
244 Once you find where the bug happened, by inspecting its location,
247 In order to report it upstream, you should identify the bug tracker, if any, or
251 For example, if you find a bug at the gspca's sonixj.c file, you can get
254 	$ ./scripts/get_maintainer.pl --bug -f drivers/media/usb/gspca/sonixj.c
271 - The bug reporting URIs for the driver/subsystem (none in the above example).
273 If the listing contains bug reporting URIs at the end, please prefer them over
283 Fixing the bug
286 If you know programming, you could help us by not only reporting the bug,