A few full stops and some line spacing. Rob
Index: faq2.html =================================================================== RCS file: /cvs/www/faq/faq2.html,v retrieving revision 1.127 diff -u -p -r1.127 faq2.html --- faq2.html 2 Jul 2015 05:49:04 -0000 1.127 +++ faq2.html 10 Sep 2015 14:47:30 -0000 @@ -117,7 +117,7 @@ a message body of "help". <p> Your subscription to the OpenBSD mail lists can also be maintained through the web interface at - <a href="http://lists.openbsd.org";>http://lists.openbsd.org</a> + <a href="http://lists.openbsd.org";>http://lists.openbsd.org</a>. <p> Some of the more popular OpenBSD mailing lists @@ -345,7 +345,7 @@ characters?</h3> <p> This is helpful to get the man page straight, with no non-printable -characters.<br> +characters.<p> Example: <blockquote> @@ -641,7 +641,7 @@ ddb> <b>show panic</b> ddb> </pre></td></tr></table> <p> -In this case, the panic string was "Kernel: page fault trap, code=0" +In this case, the panic string was "Kernel: page fault trap, code=0". <p> <b>Special note for SMP systems:</b><br> @@ -709,7 +709,7 @@ ddb> This tells us what function calls lead to the crash.<p> -To find out the particular line of C code that caused the crash, you can do the following:<br> +To find out the particular line of C code that caused the crash, you can do the following:<p> Find the source file where the crashing function is defined in. In this example, that would be pf_route() in sys/net/pf.c. Recompile that source file with debug information:<p> @@ -732,7 +732,7 @@ In the output, grep for the function nam </pre></td></tr></table><p> Take this first hex number and add the offset from the 'Stopped at' line: -<b>0x7d88</b> + <b>0x263</b> == <b>0x7feb</b>.<br> +<b>0x7d88</b> + <b>0x263</b> == <b>0x7feb</b>.<p> Scroll down to that line (the assembler instruction should match the one quoted in the 'Stopped at' line), then up to the nearest C line number:<p>
