#163 GDB of TDM-GCC 4.7.1 x64 returns 'ImportError: No module named site'

[orwelldevcpp]

Report
Although this might not be strictly related to TDM, the GDB supplied with TDM-GCC 4.7.1-2 x64 won't start, and returns "ImportError: No module named site". This makes debugging, well, impossible with the current 4.7.1 x64 build.

Research
Google tells me this is some python dependency, and I do not have Python installed, nor am I planning to. I also don't want to force the users I supply your compiler (via Dev-C++) to install Python either.

Google also suggested removing anything related to python from Environment variables, but that didn't work. Also, this is the first time I've seen GDB being explicitly dependent on python dlls, which might be related.

Question
By the way, can I (Dev-C++) simply replace the supplied GDB by, for example, the GDB from TDM32? In other words: is GDB independent of GCC?

[orwelldevcpp]

I still can't use GDB in the hotfixed TDM-GCC 4.7.1-2, downloaded using "tdm64-gcc-4.7.1-2.exe", and letting the installer check for updates. Same error, same problem.

[Anonymous]

Same problem here on Windows 7 x64. To debug a 64-bit process you need the 64-bit debugger

[John E.]

Sorry for the confusion. The new GDB 7.5 build does include Python support, but it certainly wasn't my intent to force a separate Python installation on anyone.

I've released a new GDB package that includes a few additional Python library files which allow GDB to run. I'm not sure if it will break anything for the people who actually want to use Python within GDB, but for the people who don't it will allow GDB to work even without a true Python installation.

As always, the TDM-GCC installer can check for updated files on the TDM-GCC server and install the new GDB version automatically.