http://bugs.winehq.org/show_bug.cgi?id=16757
--- Comment #26 from Paul "TBBle" Hampson Paul.Hampson@Pobox.com 2009-01-05 05:08:58 --- That looks like a +snoop,+mshtml,+shdocvw trace, not a +mshtml,+shdocvw trace, which would explain why it's so big...
Also, it looks like you're running it from within a git tree using the wine symlink created during build. That won't work with Wine-Gecko 0.9.0 (see bug 16785)
You should be doing something like: WINEDEBUG=+shdocvw,+mshtml wine hl.exe > logfile 2>&1 from within your CS directory.
If this is running from Steam, then do the above, but we really don't want the part before CS is started. (See the Wiki for a suggestion on how to do this using pipes)
I also don't see any obvious crash cause here, but I don't see the complaint about loading Gecko from the earlier backtrace either.
I'm guessing the crash is what caused the seh exception and the MiniDumpWriteDump method to complete, but I don't see anything that caused that.