X-Spam-Check-By: sourceware.org Date: Tue, 30 May 2006 22:58:57 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 20060529: python and semaphores Message-ID: <20060531025857.GA20999@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <447CFD10.3030404@users.sourceforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447CFD10.3030404@users.sourceforge.net> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, May 30, 2006 at 09:18:56PM -0500, Yaakov S (Cygwin Ports) wrote: >While attempting to package eric3, python (2.4.3-1) just segfaults on >the included install.py script before it can do anything else. This >used to work with cygwin-1.5.18-1 and python-2.4.1-1, and since I've >had similar problems with cygwin-1.5.19-4 and python-2.4.1-1, I'm >fairly sure that cygwin1.dll (both 1.5.19-4 and 20060529 snapshot) is >the culprit here. > >Note that python is otherwise working normally (e.g. distutils, >pygtk2, etc.). > >I've attached the install.py script, its backtrace, and cygcheck >output. Unless I'm missing something, the backtrace is useless and probably doesn't show a real problem. It is just YA example of the "OMG! I get SIGSEGV's in GDB!!!!" problem which we must discuss every day here. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/