Advanced Search
Welcome to Omgili,
Omgili (Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.

This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.

Biggest windbg pet peeve

What is your biggest pet peeve related to the windbg debugger from microsoft? (note: I actually really like windbg if I ignore the unpolished UI.)

The ridiculous behavior when you attempt to use click-drag to select text on a line that is wider than its physical window. The pieces of the history window that I need to copy/paste into bug reports are frequently wider than the physical window.

I've gotten so used to the triple-click workaround that I find myself attempting to misuse triple click in other (well behaved) applications.

Key presses are ignored while the focus is in a source window.

It's not like you can edit the source code from inside windbg.

At least there's the Alt-1 workaround.

How insanely slow .kdfiles copies new binaries across the 1394 connection.

It can take up to one minute for a large dll.

Attempting to dock a window is almost always the wrong kind of dock the first time until :I move the mouse just right.

Why can't it have the docking cues that VS2008 has?

Discussion Title: Biggest windbg pet peeve
Title Keywords: Biggest  windbg  peeve