cobaltfusion/debugviewpp

DebugView++, collects, views, filters your application logs, and highlights information that is important to you!

debugviewpp's Issues

Change tab-background color if new filtered item is found

When multiple tabs are open, it is useful to see if new information is available in a tab without having to periodically check all tabs

Disable colomns

Can we have a context menu for the listview headers to show/hide colomns?

Parse message into separate colomns

Just an idea, might be useful to someone :-)

F3 to 'find next'

Bind F3 key to the find-next function
Also bind shift-F3 to the find-previous function

Store the messages in compressed memory

Less resources would required if we compress messages using for example Google snappy https://code.google.com/p/snappy/

A fast and easy way to handle this is to use a fixed lines-size block buffer.
This way compression/decompression is clustered in a way that it is only needed when blocksize is reached to both reads and writes.

pseudo code:
create a vector writeBuffer
and when writeBuffer.size() == blocksize compress the writeBuffer and store it in vector< buffer* > mBlocks

see https://code.google.com/p/buggazer/source/browse/source/BugGazer/Storage/SnappyBlocks.cs

specifically, the method string GetText(int stringId)

Ignore filter

This type of filter would prevent lines from auto-scrolling your view, so the view scrolls down only if relevant new information is comes in.

Minimize to tray feature

Useful if you want debugview++ to keep keep in the background.

Selecting just 2 lines does not work

Always on top option

Do not make this default :)

Group messages by ThreadID using coloring

This could be done by logging the threadID in the message, for example:

Foo::doFoo(1, 2, 3) enter (tid: 1234)
dummy message (tid: 555)
dummy message (tid: 555)
Foo::doBar(1, 2) enter (tid: 1234)
dummy message (tid: 666)
dummy message (tid: 666)
Foo::doBar(1, 2) leave -> 4 (tid: 1234)
Foo::doBar(1, 2) leave (tid: 1234)

It would be useful to follow the code-flow if the lines from the same TID could have the same color or where indented at the same level:

    Foo::doFoo(1, 2, 3) enter (tid: 1234)
dummy message (tid: 555)
dummy message (tid: 555)
    Foo::doBar(1, 2) enter (tid: 1234)
dummy message (tid: 666)
dummy message (tid: 666)
    Foo::doBar(1, 2) leave -> 4 (tid: 1234)
    Foo::doBar(1, 2) leave (tid: 1234)

Prevent merging GetLines data from localReader+globalReader on UI thread

Using a WaitForMultipleObjects for all logsources we could do this, mostly already implemented.

optionally save settings as xml or ini to make configuration portable

Default filter to prevent 'system noise'

Filter 'devenv.exe' message, empty lines,

Info: AfxDllCanUnloadNow returning S_OK

Log to file + Logfile maximum size

Feature to stream the logging directly to a file, that can then be monitored remotely using any kind of sharing mechanism, specifically, a program like WinTail (http://tailforwin32.sourceforge.net/ ) should be able to monitor the file. That means a second process should be able to read the file while debugview++ is writing to it.

Open file

Open an existing file to do post-mortom filtering

ProcessName is not resolved if the process has died since the message was sent.

Maybe we should keep a cache of process handles of all running processes to be able to resolve these?

Openprocess reports 'The parameter is incorrect' sometimes

trigger custom action filter

a matching filter of this type would start a custom action, like a messageBeep or an executable with the pid+msg as parameters.

Minus-Key to add exclude filter of process of selected message

Select by dragging the cursor over message text

Allow to select a piece a message bigger then just a word

Stop scrolling filter

Filter that when matched stops the auto-scroll feature.
Example: stop on "Shutting down the rootbrickbox" or the first line that contains the work 'exception'

Drag selection works only on message

it is also useful to select (part of) the process name, pid or timestamp.

play/pause behaviour of global reader

The pause behavior is non-functional for the global-reader

Bolding for token filter?

Allow the token highlighting to change to font to bold

Bookmarks

Pressing CTRL- (0-9) will bookmark the selected line.
Pressing (0-9) will jump back to the bookmarked line.

These keyboard keys (0-9) conflicts with the SAIT search-as-I-type feature, so CTRL (0-9) could be used instead.

Pass-through feature

Debugview++ now monitors the DBWinMutex to receive the Outputdebugstring messages. See http://www.unixwiz.net/techtips/outputdebugstring.html for an explanation to this mechanism. When a debugging tool (like visual studio) is attached to the process Debugview++ will nolonger receive any messages.

Also a second client (let's say BugGazer https://code.google.com/p/buggazer/ ) would contest for the DBWinMutex and both clients end up receiving only some of the messages.

This could be resolved by API hooking into the Kernel32 OutputDebugStringA method, also this would allow us to call the original API as well, so DBWinMutex based clients would also receive the messages.

SAIT does not work for keywords outside view

Smart find-next (f4?)

pressing 'smart find-next (F4?) after selecting a highlighted line jumps to the next line with the same highlighting.

Key to move to next highlighed item

Move the next highlighted item would be useful, then a 'exceptions' TAB can be made to highlighting only 'exceptions'. If you switch to this tab and press a key the next (or last available) hightlighted item (exception) is shown

underscores are rendered below the previous character

If filter is renamed, the name is not updated until the cursor hovers over the tab

Highlighting problems with tabbed text

The string position matching doesn't always use the tabified text.

find and match keyword

If a keyword is found, and later the same keyword appears again, make it underlined and clickable to jump the previous appearance of the keyword.

Different application / implementation:

Find a logged memory address:

0001 Allocated object 'foo' 0x12341234 at Foo::CreateObject (Foo.cpp:24)
.....
1000 Memory leaks detected:
1001 block of 24 bytes at 0x12341234

Hovering the mouse above the second occurrence (and now highlighted) of 0x12341234 would should show the first message at (1) in a tooltip

Hidden columns get a width of 0 instead of being removed

Tracking item

Filter that selects and centers the found item each time it is found, allowing you to continuously monitor an item in its context.

Cursur position is lost when filters are updated

parsing: parse by separator to create colomns

example:

test;123;bla;foo;bar

log this in separate colomns.

Context menu option to 'exclude process'

1 [ Exclude this process ]
2 [ Exclude processname ]

Option 1:
This should add a filter to exclude the process by its handle so when a new process is started with the same name, or the PID of the current process is re-used its output is not filtered.

Option 2:
This should add a filter to exclude the process that produced the line by its full executable name.

DebugView does not close on Windows 7

DebugView does not close on Windows 7
if UpdateColumnWidths(); in CLogView::SaveSettings is enabled (uncommented)

If have tested this on my workstation at FEI and reproduced the behavior on a local laptop that hosts Windows 7.

Install uncaught exception handler to make sure the application never closes without saving logs.

Mark all existing logging as 'old' graying it

Could be useful to mark the beginning of a new test-attempt, when you want to keep the older logging for reference

LocalReader() en GlobalReader() output times out-of-order when Lines collections overlap

Bookmarks are cleared if filter is updated

DBGVIEWCLEAR support

Clear-output string: When DebugView sees the special debug output string "DBGVIEWCLEAR" it clears the output.

Show SAIT (Search-As-I-Type) status

While you type you cannot see any difference between a type and a good keyword where the result is not found.
Maybe we could show in de statusbar:

'term' not found....
'term' found at line xxx

autonewline does not work correctly for multiple processes

Commandline options to start minimized, log to a file and limit resource consumption

/m minimized
/L [,]
/M

Circular buffering for optimal performance

A circular buffer would reduce dynamic memory allocation and prevent the need to merge logsources

Prevent heavy processing on UI thread in LogView::Add

GetTextColor and GetHighlights are now executed for each incoming line, this should only be done (and cached) per view

We need a way to un-highlight SAIT keywords