Dear all,
You have to know the behavior of DbgView.
Assume I have one AP and one driver, the driver has a lot of debug messages.
The AP also has debug messages.
Assume there are too many debug messages so they can not read-time show in DbgView.
But in Windows debugging mechanism, (or DbgView mechanism?), these debug message will not lose. They just appear in DbgView later.
But please note their timestamp still keep the exact timestamp and DbgView will sort them by their timestamp!
For example,
In time 00:10, the DbgView look like that:
00:08.00 [Driver] foo bar!
00:09.00 [Driver] foo bar!
00:10.00 [AP] foo your bar! Shut up!
But if AP no longer output debug message, wait for a while, you will see a lot of debug message "inserted" between 00:09.00 and 00:10.00. Like that:
00:08.00 [Driver] foo bar!
00:09.00 [Driver] foo bar!
00:09.01 [Driver] foo bar!
00:09.02 [Driver] foo bar!
00:09.03 [Driver] foo bar!
00:09.04 [Driver] foo bar!
00:09.05 [Driver] foo bar!
00:09.06 [Driver] foo bar!
00:09.07 [Driver] Ohla~Ohla~Ohla~Ohla~Ohla~Ohla~! (See comic "JoJo's adventure")
00:10.00 [AP] foo your bar! Shut up!
So, if your driver has a lot of debug message, wait for a while, wait until all its messages output!
Frank
No comments:
Post a Comment