From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22596 invoked by alias); 29 Sep 2011 04:07:05 -0000 Received: (qmail 22578 invoked by uid 22791); 29 Sep 2011 04:07:01 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Sep 2011 04:06:45 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 4FA3A2BB4F3; Thu, 29 Sep 2011 00:06:45 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Y7ys275CHRCT; Thu, 29 Sep 2011 00:06:45 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 2567F2BB4F0; Thu, 29 Sep 2011 00:06:44 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 97234145615; Thu, 29 Sep 2011 00:06:34 -0400 (EDT) Date: Thu, 29 Sep 2011 04:47:00 -0000 From: Joel Brobecker To: John Spencer Cc: gdb-patches@sourceware.org Subject: Re: [RFC] Crash sourcing Python script on Windows Message-ID: <20110929040634.GD19246@adacore.com> References: <1317251996-12146-1-git-send-email-brobecker@adacore.com> <09787EF419216C41A903FD14EE5506DD03098D555B@AUSX7MCPC103.AMER.DELL.COM> <4E83D440.6000702@barfooze.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E83D440.6000702@barfooze.de> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00499.txt.bz2 > FILE is supposed to be an opaque type and as such noone except of > the libc which defines it is supposed to "poke" at its internals. > however it is common practice in GNU software to assume everybody > uses GLIBC and poke around in internal stuff thats not supposed to > be accessibly at all in userland. It could be something simpler than that. Python was built on one system, using an unknown build environment. when then use that library to link it against some code on a version of Windows that is most likely different, with a compiler that is also most likely different. If each compiler used a libc where the definition of that type is different, then we have an incompatibility. -- Joel