Lines Matching refs:good
10 This document is intended to give a good overview of how to debug Linux for
188 vector table. This is a good thing & does simplify some of the kernel coding
760 you get good at it.
764 felt that it was a good idea not to go over the 80 columns on the screen.
766 decode mentally and you can make a good guess at a lot of them as all the
904 script with breakpoints on every kernel procedure, this isn't a good idea
909 in the file menu called "Save Screen In File" - this is very good for keeping a
1114 under VM ( unless you are good at decoding ASCII in your head ).
1493 A good trick is tracing all the IO's and CCWS and spooling them into the reader
1585 Note gdb's online help is very good use it.
1682 is inconsistent & not very good, watchpoints usually work but not always.