patch-2.1.99 linux/Documentation/oops-tracing.txt

• Lines: 9
• Date: Tue Apr 28 14:22:04 1998
• Orig file: v2.1.98/linux/Documentation/oops-tracing.txt
• Orig date: Fri Sep 6 09:19:04 1996

diff -u --recursive --new-file v2.1.98/linux/Documentation/oops-tracing.txt linux/Documentation/oops-tracing.txt
@@ -41,7 +41,7 @@
 disassembly.
 
 Now, the trick is just then to combine all the data you have: the C 
-sources (and general knowledge of what it _should_ do, the assembly 
+sources (and general knowledge of what it _should_ do), the assembly 
 listing and the code disassembly (and additionally the register dump you 
 also get from the "oops" message - that can be useful to see _what_ the 
 corrupted pointers were, and when you have the assembler listing you can