Re: [RFC] Crash sourcing Python script on Windows

Eli Zaretskii
2011-09-29T07:11:18Z

> From: <Paul_Koning@Dell.com>
> Date: Wed, 28 Sep 2011 20:01:20 -0500
>
> That sounds like a good solution.

I agree, FWIW. I tried to source a Python script on my Windows box
(with Python26.dll), and sure thing, GDB crashed.

> I'm puzzled though -- how did FILE end up being different? One would expect the right header files to be used, producing correct/consistent results. If that didn't happen in this case, could it happen for other aspects of the GDB to Python API?

Python.org builds Python for Windows using the Microsoft compiler. (I
have no idea why they use a proprietary compiler when a free one is
available and rock solid.) By contrast, GDB is built using MinGW
runtime and headers. The ABI is completely compatible AFAIK, but some
incompatibilities can still lurk, especially in data types internal to
the library. I agree that it's strange to see such an incompatibility
in the FILE object. Joel, could you provide some details about this
incompatibility? Perhaps we could use some GCC switch while building
GDB, to work around this? (The -mms-bitfields switch comes to min.)