delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY |
X-Spam-Check-By: | sourceware.org |
X-Yahoo-SMTP: | jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- |
Date: | Fri, 20 May 2011 01:44:20 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Issues with latest rtorrent under Win7 x64 when attempting to package |
Message-ID: | <20110520054420.GA17408@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <BANLkTineFxeJDfAXCRejDPpWkDgRxkA51g AT mail DOT gmail DOT com> <BANLkTinyBgQuYu3VAyzss2PNB7WApOE-yQ AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <BANLkTinyBgQuYu3VAyzss2PNB7WApOE-yQ@mail.gmail.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
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 Thu, May 19, 2011 at 10:01:47PM -0400, Chris Sutcliffe wrote: >On 19 May 2011 11:40, Chris Sutcliffe wrote: >> I've built the latest libtorrent / rtorrent, packaged it and tested it >> on WinXP x86 with no issues. ?I then attempted to test on Win7 x64 and >> it's crashing constantly. ?I've disabled Windows Defender and >> uninstalled my antivirus software, done a rebaseall, and nothing seems >> to help. ?I'd appreciate any pointers on what to try next, as I'm at a >> bit of a loss. > >Creating a debug build hasn't helped either. When it crashes it's >causing a stack dump, so doing a 'bt' in gdb just returns 'no stack'. That probably means that it's forking. You're debugging the parent when the child is having problems. The addresses in the stack dump can be decoded with gdb: l *0xnnnnn ^ that's an "ell". cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |