Comment 12 for bug 490228

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

Gareth White wrote:
> Thanks John. Unfortunately those ones are built against Python 2.6
> rather than 2.5 which the official Bazaar installation for Windows uses,
> so they don't work as drop-in replacements. I tried using your patch to
> rebuild the extensions against 2.5 but that requires Visual Studio 2003
> which I don't think we have installed anywhere here!
>
> If you're able to build a binary (plus pdb) of groupcompress from Bazaar
> 2.0.1 that's compatible with 2.5 I'll give it a go and see if I can get
> it to crash again. Alternatively I could try building all the extensions
> against 2.6 with Visual Studio 2005 and see if I can get that to crash.
> That's not really an ideal test though because it's changing too many
> variables at once.
>
> It would be handy if debug symbols were built for every release of
> Bazaar and either included in the installer or provided as a separate
> zip file, as that would make debugging crashes like this a lot easier.
> I'll enter a bug for that.
>

I also found this link:

http://stackoverflow.com/questions/866721/how-to-generate-gcc-debug-symbol-outside-the-build-target

Which would be a way to always compile with debug flags, and then split
them into 2 parts. So that you can then download the debug information
later.

However, for what I'm doing, I'm just going to use -g.

On the flip side, I don't know that WinDBG knows anything about gcc
debug data. But it is at least worth a shot.

Anyway, attached is a python 2.5 version with -g enabled. You can try it
out and see if it helps.

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

iEYEARECAAYFAksX5pIACgkQJdeBCYSNAAN4/QCgvJdarCHCuABkaryzKT0gvs5Y
t/0An1Ee63qdhL5N/Yihq6nsrtLLVe0G
=19nR
-----END PGP SIGNATURE-----