CapsUnlock Logging

by andyjmay December 11, 2011

There is some simple logging inside of CapsUnlock to help me debug any potential errors that might creep up. It logs some critical events that occur in the application to a text file in the installation path. This file is not sent anywhere, and no personal information is collected. Here is a sample log file:

12/11/2011 9:30:21 PM | Initialized PID cache
12/11/2011 9:30:21 PM | Clearing the PID cache
12/11/2011 9:30:21 PM | Cleared the PID cache
12/11/2011 9:30:21 PM | Starting CapsLockWatcher on cmd
12/11/2011 9:30:21 PM | Found process (filezilla) with PID: 7000
12/11/2011 9:30:21 PM | Added filezilla (7000) to PID cache
12/11/2011 9:30:26 PM | Found process (explorer) with PID: 2152
12/11/2011 9:30:26 PM | Added explorer (2152) to PID cache
12/11/2011 9:30:27 PM | Found process (capsunlock) with PID: 7732
12/11/2011 9:30:27 PM | Added capsunlock (7732) to PID cache
12/11/2011 9:30:33 PM | Found process (notepad++) with PID: 9184
12/11/2011 9:30:33 PM | Added notepad++ (9184) to PID cache
12/11/2011 9:30:53 PM | Found process (vcsexpress) with PID: 8240
12/11/2011 9:30:53 PM | Added vcsexpress (8240) to PID cache
12/11/2011 9:30:59 PM | Unable to find a process with PID: 0
12/11/2011 9:30:59 PM | Found process (thgw) with PID: 7100
12/11/2011 9:30:59 PM | Added thgw (7100) to PID cache
12/11/2011 9:32:15 PM | Found process (chrome) with PID: 7748
12/11/2011 9:32:15 PM | Cleared the PID cache
12/11/2011 9:32:15 PM | Added chrome (7748) to PID cache
12/11/2011 9:32:40 PM | Unable to find a process with PID: 0
12/11/2011 9:32:40 PM | Found process (thgw) with PID: 7100
12/11/2011 9:32:40 PM | Added thgw (7100) to PID cache
12/11/2011 9:33:26 PM | Unable to find a process with PID: 0
12/11/2011 9:39:16 PM | Unable to find a process with PID: 0
12/11/2011 9:39:16 PM | Found process (explorer) with PID: 2152
12/11/2011 9:39:16 PM | Cleared the PID cache
12/11/2011 9:39:16 PM | Added explorer (2152) to PID cache
12/11/2011 9:39:18 PM | Found process (chrome) with PID: 7748
12/11/2011 9:39:18 PM | Added chrome (7748) to PID cache
12/11/2011 9:39:19 PM | Unable to find a process with PID: 0
12/11/2011 9:39:19 PM | Found process (thgw) with PID: 7100
12/11/2011 9:39:19 PM | Added thgw (7100) to PID cache
12/11/2011 9:39:21 PM | Found process (paintdotnet) with PID: 6136
12/11/2011 9:39:21 PM | Added paintdotnet (6136) to PID cache
12/11/2011 9:39:27 PM | Unable to find a process with PID: 0
12/11/2011 9:48:20 PM | Unable to find a process with PID: 0
12/11/2011 9:48:20 PM | Found process (notepad++) with PID: 9184
12/11/2011 9:48:20 PM | Cleared the PID cache
12/11/2011 9:48:20 PM | Added notepad++ (9184) to PID cache
12/11/2011 9:48:24 PM | Found process (chrome) with PID: 7748
12/11/2011 9:48:24 PM | Added chrome (7748) to PID cache
12/11/2011 9:48:26 PM | Found process (explorer) with PID: 2152
12/11/2011 9:48:26 PM | Added explorer (2152) to PID cache
12/11/2011 9:48:27 PM | Found process (capsunlock) with PID: 7732
12/11/2011 9:48:27 PM | Added capsunlock (7732) to PID cache
12/11/2011 9:48:28 PM | Stopping CapsLockWatcher
12/11/2011 9:48:28 PM | Closing...

Opening the log file is a hidden feature (on purpose, this should only be necessary in debugging). If you hit CTRL + L it will open the log file in a text editor. If you ever encounter any bugs/crashes please save a copy of your log file and upload it to a new Bitbucket Issue.

blog comments powered by Disqus

Month List

Page List

Tag cloud