| 1 |
fox2mike 05/07/14 09:54:37 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en/draft debugging-howto.xml |
| 4 |
Log: |
| 5 |
Coding Style + Doublespace fixes. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.4 +19 -18 xml/htdocs/doc/en/draft/debugging-howto.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/debugging-howto.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/debugging-howto.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/debugging-howto.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo |
| 13 |
|
| 14 |
Index: debugging-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v |
| 17 |
retrieving revision 1.3 |
| 18 |
retrieving revision 1.4 |
| 19 |
diff -u -r1.3 -r1.4 |
| 20 |
--- debugging-howto.xml 14 Jul 2005 09:42:27 -0000 1.3 |
| 21 |
+++ debugging-howto.xml 14 Jul 2005 09:54:37 -0000 1.4 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v 1.3 2005/07/14 09:42:27 swift Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v 1.4 2005/07/14 09:54:37 fox2mike Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/debugging-howto.xml"> |
| 29 |
<title>Gentoo Linux Debugging Guide</title> |
| 30 |
@@ -423,9 +423,9 @@ |
| 31 |
<body> |
| 32 |
|
| 33 |
<p> |
| 34 |
-<c>dmesg</c> is a system program created with debugging kernel operation. It |
| 35 |
+<c>dmesg</c> is a system program created with debugging kernel operation. It |
| 36 |
basically reads the kernel messages and keeps them in buffer, letting the user |
| 37 |
-see them later on. Here's an example of what a dmesg output looks like: |
| 38 |
+see them later on. Here's an example of what a dmesg output looks like: |
| 39 |
</p> |
| 40 |
|
| 41 |
<pre caption="dmesg sample output"> |
| 42 |
@@ -463,12 +463,12 @@ |
| 43 |
</pre> |
| 44 |
|
| 45 |
<p> |
| 46 |
-The dmesg displayed here is my machine's bootup. You can see harddrives and |
| 47 |
+The dmesg displayed here is my machine's bootup. You can see the hard disks and |
| 48 |
input devices being initialized. While what you see here seems relatively |
| 49 |
-harmless, <c>dmesg</c> is also good at showing when things go wrong. Let's take |
| 50 |
-for example an IPAQ 1945 I have. After a couple of minutes of inactivity, the |
| 51 |
-device powers off. Now, I have the device connected into the USB port in the |
| 52 |
-front of my system. Now, I want to copy over some files using libsynCE, so I go |
| 53 |
+harmless, <c>dmesg</c> is also good at showing when things go wrong. Let's take |
| 54 |
+for example an IPAQ 1945 I have. After a couple of minutes of inactivity, the |
| 55 |
+device powers off. Now, I have the device connected into the USB port in the |
| 56 |
+front of my system. Now, I want to copy over some files using libsynCE, so I go |
| 57 |
ahead and initiate a connection: |
| 58 |
</p> |
| 59 |
|
| 60 |
@@ -484,7 +484,7 @@ |
| 61 |
The connection fails, as we see here, and we assume that only the screen is in |
| 62 |
powersave mode, and that maybe the connection is faulty. In order to see what |
| 63 |
truly happened, we can use <c>dmesg</c>. Now, <c>dmesg</c> tends to give a |
| 64 |
-rather large ammount of output. One can use the <c>tail</c> command to help |
| 65 |
+rather large ammount of output. One can use the <c>tail</c> command to help |
| 66 |
keep the output down: |
| 67 |
</p> |
| 68 |
|
| 69 |
@@ -497,15 +497,16 @@ |
| 70 |
</pre> |
| 71 |
|
| 72 |
<p> |
| 73 |
-This gives us the last 4 lines of the dmesg output. Now, this is enough to give |
| 74 |
-us some information on the situation. It seems that in the first 2 lines, the |
| 75 |
-pocketpc is recognized as connected. However, in the last 2 lines, it appears |
| 76 |
-to have been disconnected. With this information we check the pocketpc again, |
| 77 |
-and find out it is powered off, and now know about the powersave mode. We can |
| 78 |
-use this information to turn the feature off, or be aware of it next time. |
| 79 |
-While this is a somewhat simple example, it does go to show how well dmesg can |
| 80 |
-work. However, in more complex examples (such as kernel bugs), the entire dmesg |
| 81 |
-output may be required. To obtain that, simple redirect to a log file as such: |
| 82 |
+This gives us the last 4 lines of the <c>dmesg</c> output. Now, this is enough |
| 83 |
+to give us some information on the situation. It seems that in the first 2 |
| 84 |
+lines, the pocketpc is recognized as connected. However, in the last 2 lines, it |
| 85 |
+appears to have been disconnected. With this information we check the pocketpc |
| 86 |
+again, and find out it is powered off, and now know about the powersave mode. We |
| 87 |
+can use this information to turn the feature off, or be aware of it next time. |
| 88 |
+While this is a somewhat simple example, it does go to show how well |
| 89 |
+<c>dmesg</c> can work. However, in more complex examples (such as kernel bugs), |
| 90 |
+the entire <c>dmesg</c> output may be required. To obtain that, simple redirect |
| 91 |
+to a log file as such: |
| 92 |
</p> |
| 93 |
|
| 94 |
<pre caption="Saving dmesg output to a log"> |
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
-- |
| 99 |
gentoo-doc-cvs@g.o mailing list |
Archives