Comment 16 for bug 490228
Revision history for this message
| Gareth White (gwhite-deactivatedaccount) wrote | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I had assumed the 2.5 builds were using VS2003 because the pyd files depended on msvcr71.dll. However, that must be due to some other reason. BTW, is there any reason why the standalone Bazaar installer uses 2.5 rather than 2.6?
In any case, I'm pretty sure WinDbg doesn't know how to interpret gcc debug info. I could probably use gdb but I'd have to reproduce the crash using the new pyd file.
I was able to force WinDbg to load Alex's pdb but I'm not sure the stack trace is correct. So I'm going to see if I can get it to crash again overnight using his pyd file. If not, I'll retry with gdb and John's one.