Comment 18 for bug 490228

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gareth White wrote:
> 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?
>

Mingw also knows how to depend on msvcr71.dll when building python
extensions. I think it even works for python2.6, but since there is
VS2008EE and it is currently publicly available, we use it to build the
2.6 extensions.

We use 2.5 because... we haven't updated yet. :)

Also, the last time I tried 2.6, it used an updated PyQt, and that
didn't play nicely with py2exe. (Specifically, PyQt had py3k
compatibility code, which py2exe then wanted to load. And when it tried,
it crashed because the syntax isn't valid py2.6 code. And if I taught
py2exe not to include that submodule, it would then fail saying that it
was missing a necessary submodule...)

> 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.
>

Can you include the stack trace just in case? It is also possible that
adding optimizations will cause the stack trace to be hard to interpret.
However, if it fails with both my .pyd and the one Alexander built, then
it is likely to be a genuine bug in the code, and hopefully any stack
trace will help us track it down.

I don't know if you've answered this, but do you have a clear way to
reproduce it? Is it possible for us to have access to that data?

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksdW+EACgkQJdeBCYSNAAMQrQCfZQXROUlWX/RNlGurSAFDPnIw
YmcAoLw7/3qlcPp0w58CvbxbgLNu8Te1
=+uj+
-----END PGP SIGNATURE-----