From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26778 invoked by alias); 29 Sep 2011 07:11:18 -0000 Received: (qmail 26769 invoked by uid 22791); 29 Sep 2011 07:11:16 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Sep 2011 07:11:02 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LS900100VT1FN00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Thu, 29 Sep 2011 10:10:08 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.8.215]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LS9001HCVWV7N60@a-mtaout20.012.net.il>; Thu, 29 Sep 2011 10:10:08 +0300 (IDT) Date: Thu, 29 Sep 2011 07:20:00 -0000 From: Eli Zaretskii Subject: Re: [RFC] Crash sourcing Python script on Windows In-reply-to: <09787EF419216C41A903FD14EE5506DD03098D555B@AUSX7MCPC103.AMER.DELL.COM> To: Paul_Koning@Dell.com Cc: brobecker@adacore.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83y5x7esdp.fsf@gnu.org> References: <1317251996-12146-1-git-send-email-brobecker@adacore.com> <09787EF419216C41A903FD14EE5506DD03098D555B@AUSX7MCPC103.AMER.DELL.COM> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-09/txt/msg00502.txt.bz2 > From: > 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.)