Slaying the Virtual Memory Monster (If help for a problem someone has, juice it I should)

Just after the OutOfMemory monster raised it’s head, was slayed and is now believed to have vanished in the test lab, Tess posted a link to a great graphical address space analysis tool that can actually visualize the cut that mscomctl.ocx and it’s followers tear through my virtual memory blanket.

However, I wish there would be a better and standard way to integrate such great graphical tools with the debugger. A single picture says more than thousand lines of obscure command line responses.

Advertisements
This entry was posted in Coding Horror. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s