You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* This project is in low-maintenance mode, this means new features are only added if PRs are provided with tests.
8
-
* Updates are limited to keeping the status-quo and OS-related updated.
9
-
* I'm looking for maintainers, so if you would like to join me in bugfixing or adding features, please let me know.
10
-
* 2022 update: The project was migrated to VS2022 and boost 1.80, WindowsXP (32 bit) support was removed.
11
-
* the OutputForwarder companion extension for VS2022 can be found in the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=JanWilmans.OutputForwarder2022)
12
-
* nuget.exe can be downloaded from https://www.nuget.org/downloads
- new features: capture kernel messages, verbose mode and pass-through mode, big thanks to x64bugreport and 593749519 for providing information, contributions and test scenarios.
10
+
- fixed #365: support for messages from UWP applications (poorly tested), feedback welcome!
11
+
- fixed #396: depending on the runtime dlls, this broke when we moved to cmake, now we link the runtime statically again.
12
+
- fixed title bar not being updated when 'Global Win32' was toggled.
13
+
- new commandline argument /tab:<name> to select a tab that get focus at startup, contributed by KirisameMarisa
14
+
- removed color support from 'include' filter by request (a highlight filter can still achieve the same result), contributed by Ishmaeel.
- This project is in low-maintenance mode, this means new features are only added if PRs are provided with tests.
20
+
- Updates are limited to keeping the status-quo and OS-related updated.
21
+
- I'm looking for maintainers, so if you would like to join me in bugfixing or adding features, please let me know.
22
+
- 2022 update: The project was migrated to VS2022 and boost 1.80, WindowsXP (32 bit) support was removed.
23
+
- the OutputForwarder companion extension for VS2022 can be found in the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=JanWilmans.OutputForwarder2022)
24
+
- nuget.exe can be downloaded from https://www.nuget.org/downloads
We use Incredibuild to make use of all cores of multiple machines to accelerate building our C++ projects.
59
67
60
-
So when is this Debugview++ thing useful?
61
-
------------------------------------------
68
+
## So when is this Debugview++ thing useful?
62
69
63
70
- first of all, with debugview++ you can see messages from different processes, not just 'attached' processes.
64
71
- also: filtering, coloring and linking. To make sense of a large amount of information humans need to filter it or order it understand it. Also it helps if important events have different colors to quickly interpret the occurring patterns.
65
72
- finally, filtering is nice, but sometimes you need to see a line in its context to understand it, this is where linked views can help to quickly switch between a fully filtered view and a fully detailed view.
66
73
67
74
New in stable version 1.8.x:
75
+
68
76
- bugfixes (namely in file-tailing)
69
77
- tested on windows 10
70
78
- last version with (official) XP support (v141_xp target)
@@ -74,23 +82,25 @@ New in stable version 1.8.x:
74
82
- no other new features planned, if you're missing something you need, file an issue!
75
83
76
84
Features we dream about and will create when we choose to spend the time:
85
+
77
86
- a gantt chart-like view, a horizontal timeline, with bars/flags/signs on it to identify events
78
87
- a better plugin based input system
79
88
- transparent background streaming to disk
80
89
- proper memory limits
81
90
82
91
Known issues:
92
+
83
93
- the history limit doesn't work right, this is troublesome for long-running duration-tests.
84
94
A workaround is to send 'DBGVIEWCLEAR' before each test-cycle (this clears all logs from memory).
85
95
- there is no 'pass-through' mode like the original dbgview had, if you can help me implement this, please contact me.
86
96
- same goes for catching kernel messages, help wanted.
87
97
88
-
References
89
-
----------
90
-
[OutputDebugString on MSDN](https://msdn.microsoft.com/en-us/library/windows/desktop/aa363362(v=vs.85).aspx)
98
+
## References
99
+
100
+
[OutputDebugString on MSDN](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa363362(v=vs.85).aspx>)
@@ -170,18 +179,16 @@ And connect DebugView++ using Log->Connect DebugView Agent. Note that 'Log->Conn
170
179
171
180
**Use RegexGroups + Token Highlighting**:
172
181
173
-
Suppose you want to highlight some data value in your logging, since the actually value may differ, you cannot use normal matching to highlight them. With RegexGroups you can match text _before_ or _after the actual token you want to highlight.
182
+
Suppose you want to highlight some data value in your logging, since the actually value may differ, you cannot use normal matching to highlight them. With RegexGroups you can match text _before_ or \_after the actual token you want to highlight.
Filters can be defined per view, for example choose File -> New View, and the filter dialog will popup.
186
193
Pressing OK will open a new view without any filters.
187
194
@@ -199,18 +206,18 @@ just type any word or part of a word to match.
199
206
- stop: if a matching expression is found autoscroll is turned off, all track filters will be disabled and the line is focused. Note: stop filters work only if autoscroll is on, think of a stop-filter as a single-shot track filter
200
207
- beep: a standard windows beep (configurable in config panel->sounds) is played
201
208
202
-
*Practical uses*:
209
+
_Practical uses_:
203
210
204
211
Include, exclude, once and highlight filters are the most intuitive filters to use. Track and stop can be a little confusing, let me try to give some examples.
205
212
206
213
**track**: use this filter to focus interesting lines that do not occur very often, but at a regular interval, for example, so you are monitoring a process that logs output every 30 seconds and you need to check the result.
207
214
208
215
**stop**: this filter is good when some special event occurs (an exception?) and you want to inspect the context of the event in the log before continuing. A press of the 'end' button will resume auto scrolling.
209
216
210
-
Other features:
211
-
----------------
217
+
## Other features:
212
218
213
219
**views**:
220
+
214
221
- reset view; make the first line in the logbuffer the first line in the view
215
222
- reset view to this line; make the current like the first line in the view
216
223
- clear view; make next incoming message the first line in the view
@@ -227,8 +234,7 @@ Now you can monitor the filtered view, and when your event occurs, select a line
227
234
228
235
**process colors**: If enabled each process (even processed with identical names) will get a its own background color automatically without adding any filters.
229
236
230
-
Other documentation:
231
-
--------------------
237
+
## Other documentation:
232
238
233
239
**Auto Scroll**: scrolls down to new incoming lines automatically
234
240
@@ -239,11 +245,12 @@ turned off if any other line is selected.
239
245
240
246
**ClockTime**: when enabled the time is displayed as provided by the system's real-time clock (RTC). Such a timestamp has a 16ms resolution on a typical desktop PC. When disabled, time is displayed as a relative time to the first message, however this timestamp is obtained from the High-Performance Counter (HPC) which typically has a sub-microsecond resolution.
241
247
242
-
The resolution should not be confused with accuracy here, the recorded timestamp is not the actual time the message occurred, it is the time the message was received by DebugView++. Also there is no guarantee that the time between occurrence and reception of messages is constant, *however* in practice this is **pretty** constant :)
248
+
The resolution should not be confused with accuracy here, the recorded timestamp is not the actual time the message occurred, it is the time the message was received by DebugView++. Also there is no guarantee that the time between occurrence and reception of messages is constant, _however_ in practice this is **pretty** constant :)
249
+
250
+
## How to build
243
251
244
-
How to build
245
-
------------
246
252
This project has a special configuration:
253
+
247
254
- 32bit debug/release configurations are targeted to v140_XP, SDK v7.0 (windows XP SP3 and up)
248
255
- 64bit debug/release configurations are targeted to v141, SDK v8.1 (runs on windows 7 and up)
249
256
- only the release configurations also build the Wix installer
@@ -265,7 +272,7 @@ Since we use ATL and support Windows XP still some extra installation options ar
0 commit comments