Molle Bestefich wrote:
> Joseph Galbraith wrote:
>> Yep... pretty much the standard windbg symbol server stuff
>> (that comes with the WinDBG install) will do it.
>
> Cool.
> And you don't find that your team is missing the actual .exe's?
The symbol server actually stores pdb, dlls, and exes; integrated
with the source server (which is also builtin to WinDBG and
supports SVN) I can launch a crash dump and windbg auto-magically
finds the symbols and pulls the correct source files from SVN.
Using Microsoft's symbol server, it pulls the correct OS symbols
automatically too, so I can back-trace through message loops, and
other system callbacks.
'The bag' as it is affectionately known, has come a long ways
since the bad old days when it was the dev teams unwanted child
and the IDE debugger made it look like a throw-back from the
70's.
> What if you want to reproduce the problem yourself - is a recompiled
> version good enough?
Sure, if you can generate the crash in any given version that you
built, you have the current, correct symbols for that by
definition.
Thanks,
Joseph
PS. Even Unix, if you strip the image, you'll probably what to
stash the debug information away instead of depending on being
able to rebuild. The problem is that while your source code
may be reproduced faithfully by version control, your build
environment isn't.
There is just to big a chance that their will be a security
bug in zlib and the system library will be upgraded and all
of a sudden rebuilding the source gives a slightly
different binary.
Not to pick on zlib our anything :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Apr 12 20:12:30 2006