X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 14 Feb 2008 10:28:33 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Threading issue in cygwin python 2.5.1-2 ?
Message-ID: <20080214092833.GC25954@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <46E01E3C DOT 7000506 AT cygwin DOT com> <46E02134 DOT 3030400 AT kleckner DOT net> <46E03EFD DOT 3040806 AT kleckner DOT net> <46E04E85 DOT 59E9E910 AT dessent DOT net> <479A9A8F DOT 9090106 AT kleckner DOT net> <009001c860e9$dd4a0000$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <479CEC96 DOT 1090607 AT kleckner DOT net> <47B0CCD5 DOT 30403 AT kleckner DOT net> <foql6c$j3p$1 AT ger DOT gmane DOT org> <47B32A60 DOT 5010602 AT kleckner DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47B32A60.5010602@kleckner.net>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Feb 13 09:35, Jim Kleckner wrote:
> What is the best way to proceed with this?
>
> It appears to have been a change since 1.5.18 if Jason's guess
> is correct.
>
> I can build a debug version of Python if that is useful.
> I can build a debug version of cygwin if that is useful although
> previous list comments suggest that it requires some deep
> knowledge to do/use properly.

Building cygwin from CVS requires gcc, a spare build directory (don't
build in the source dir), and the deep knowledge how to get rid of the
optimizer flag when building.  It boils down to

  Read http://cygwin.com/cvs.html
  [...]
  $ cvs co winsup
  $ mkdir ../build
  $ cd ../build
  $ ../src/configure
  $ make CFLAGS=-g CFLAGS_FOR_TARGET=-g
  Stop all Cygwin processes
  Replace /bin/cygwin1.dll with new-cygwin1.dll from your build dir.
  Copy cygwin1.dbg from the build dir to /bin.
  Start debugging.

What would be helpful is a simple testcase in plain C which does not
require an interpreter (python) to run.  The less environment, the less
code you need to reproduce a problem, the simpler to debug.

> As an off-topic side note, it sure would be nice to be
> able to use valgrind just once on cygwin!

Easy.  Just ask the valgrind guys to stop relying on non-portable Linux
features.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/