Sawbuck 0.6.8.0 released

[Sigurður Ásgeirsson]

Hi Sawbuck users and developers, 

Sawbuck 0.6.8.0 is now available for download at [http://code.google.com/p/sawbuck/downloads/detail?name=sawbuck-0.6.8.0-release.msi]. This version of Sawbuck allows you to save and restore filter settings and has some important bug fixes and tweaks, so please update your copy.

Saving and restoring filters makes it very easy to switch between settings, which is convenient if you like to carve your logs several different ways for different tasks.

This version of Sawbuck contains the following bugfixes:

• Fixes to kernel event log parsing.
  This enables stack trace symbol resolution for processes that are already running before you launch Sawbuck 64 bit machines.
• Updates the default symbol path.
  There was an error in the Microsoft symbol server path and the Chromium symbol server has moved since the last Sawbuck release.
• Improves the capture time resolution.
  Sawbuck now requests QPC (QueryPerformanceTimer) time resolution for the log sessions, which improves the time resolution at capture to sub-millisecond. Previously Sawbuck would use the default time resolution, which is ~15ms granular on most systems. Time display is still only to millisecond accuracy - if that irks you, please shoot me an email.
  

If Sawbuck doesn't display stack traces for log messages, please do this:

• Open the Provider Configuration dialog (Log->Configure Providers...). 
• Verify that the "Enable Mask" in the Provider configuration dialog has the "Stack Trace" bit enabled for your provider (Chrome), and that the "Text Only" bit is disabled.

If it does display stack traces, but doesn't resolve them to symbols, please check that Sawbuck's symbol path is valid. It should look something like this: "SRV*C:\Users\<user>\AppData\Local\Temp\symbols*http://msdl.microsoft.com/download/symbols;SRV*C:\Users\<user>\AppData\Local\Temp\symbols*http://chromium-browser-symsrv.commondatastorage.googleapis.com".

It's a known problem that Sawbuck maintains some data structures about system state that are monotonically increasing. If you leave it running long enough, it will run out of memory and crash, in which eventuality you can simply re-launch it.

Special thanks to:

• Robert Shield, who contributed saving and restoring filters
• Chris Hamilton, who fixed the kernel trace problems.

Enjoy,

Siggi