From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1Dt0Qg-0000ib-8Z for garchives@archives.gentoo.org; Thu, 14 Jul 2005 09:54:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6E9shcq031538; Thu, 14 Jul 2005 09:54:43 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6E9sgwC001103 for ; Thu, 14 Jul 2005 09:54:42 GMT Message-Id: <200507140954.j6E9sgwC001103@robin.gentoo.org> Received: from lark.gentoo.osuosl.org ([140.211.166.177] helo=lark.gentoo.org) by smtp.gentoo.org with smtp (Exim 4.43) id 1Dt0QY-0001aM-1I for gentoo-doc-cvs@lists.gentoo.org; Thu, 14 Jul 2005 09:54:46 +0000 Received: by lark.gentoo.org (sSMTP sendmail emulation); Thu, 14 Jul 2005 09:54:37 +0000 From: "Shyam Mani" Date: Thu, 14 Jul 2005 09:54:37 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: debugging-howto.xml Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: 7013b857-21af-4f31-9f1e-8b1d79ae7b7b X-Archives-Hash: 859cafdd0a20beb7754d8a61863c0355 fox2mike 05/07/14 09:54:37 Modified: xml/htdocs/doc/en/draft debugging-howto.xml Log: Coding Style + Doublespace fixes. Revision Changes Path 1.4 +19 -18 xml/htdocs/doc/en/draft/debugging-howto.xml 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 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 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 Index: debugging-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- debugging-howto.xml 14 Jul 2005 09:42:27 -0000 1.3 +++ debugging-howto.xml 14 Jul 2005 09:54:37 -0000 1.4 @@ -1,6 +1,6 @@ - + Gentoo Linux Debugging Guide @@ -423,9 +423,9 @@

-dmesg is a system program created with debugging kernel operation. It +dmesg is a system program created with debugging kernel operation. It basically reads the kernel messages and keeps them in buffer, letting the user -see them later on. Here's an example of what a dmesg output looks like: +see them later on. Here's an example of what a dmesg output looks like: 

@@ -463,12 +463,12 @@

-The dmesg displayed here is my machine's bootup. You can see harddrives and +The dmesg displayed here is my machine's bootup. You can see the hard disks and input devices being initialized. While what you see here seems relatively -harmless, dmesg is also good at showing when things go wrong. Let's take -for example an IPAQ 1945 I have. After a couple of minutes of inactivity, the -device powers off. Now, I have the device connected into the USB port in the -front of my system. Now, I want to copy over some files using libsynCE, so I go +harmless, dmesg is also good at showing when things go wrong. Let's take +for example an IPAQ 1945 I have. After a couple of minutes of inactivity, the +device powers off. Now, I have the device connected into the USB port in the +front of my system. Now, I want to copy over some files using libsynCE, so I go ahead and initiate a connection:

@@ -484,7 +484,7 @@ The connection fails, as we see here, and we assume that only the screen is in powersave mode, and that maybe the connection is faulty. In order to see what truly happened, we can use dmesg. Now, dmesg tends to give a -rather large ammount of output. One can use the tail command to help +rather large ammount of output. One can use the tail command to help keep the output down:

@@ -497,15 +497,16 @@

-This gives us the last 4 lines of the dmesg output. Now, this is enough to give -us some information on the situation. It seems that in the first 2 lines, the -pocketpc is recognized as connected. However, in the last 2 lines, it appears -to have been disconnected. With this information we check the pocketpc again, -and find out it is powered off, and now know about the powersave mode. We can -use this information to turn the feature off, or be aware of it next time. -While this is a somewhat simple example, it does go to show how well dmesg can -work. However, in more complex examples (such as kernel bugs), the entire dmesg -output may be required. To obtain that, simple redirect to a log file as such: +This gives us the last 4 lines of the dmesg output. Now, this is enough +to give us some information on the situation. It seems that in the first 2 +lines, the pocketpc is recognized as connected. However, in the last 2 lines, it +appears to have been disconnected. With this information we check the pocketpc +again, and find out it is powered off, and now know about the powersave mode. We +can use this information to turn the feature off, or be aware of it next time. +While this is a somewhat simple example, it does go to show how well +dmesg can work. However, in more complex examples (such as kernel bugs), +the entire dmesg output may be required. To obtain that, simple redirect +to a log file as such: 




-- 
gentoo-doc-cvs@gentoo.org mailing list