Comment 2 for bug 629583

I was attempting to follow your wishes, and not post a stack trace directly into the log.

I did find bzr.dmp which is probably the visual c++ crash dump file for this issue. I have tried to attach it again, but perhaps it wont be successful.

By the way, is it easy to run bzr-explorer in such a way that one can get all or some of the following.
o a python stack trace
o a c/c++ stack trace with symbols

Most of the crashes I see are maybe in c/c++ below python. Otherwise, I would see a python stack trace in the bzr-explorer dos box? I typically don't.

I could probably figure this out on my own, but like all developers I have my own issues to deal with and if there was a recipe for users to follow setting this up we might find it was much easier to help out.