public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Issues with latest rtorrent under Win7 x64 when attempting to package
Date: Fri, 20 May 2011 05:44:00 -0000	[thread overview]
Message-ID: <20110520054420.GA17408@ednor.casa.cgf.cx> (raw)
In-Reply-To: <BANLkTinyBgQuYu3VAyzss2PNB7WApOE-yQ@mail.gmail.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

  reply	other threads:[~2011-05-20  5:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 15:40 Chris Sutcliffe
2011-05-20  2:02 ` Chris Sutcliffe
2011-05-20  5:44   ` Christopher Faylor [this message]
2011-05-20 16:51     ` Chris Sutcliffe
2011-05-20 17:16       ` Christopher Faylor
2011-05-20 17:39         ` Chris Sutcliffe
2011-05-20 17:44           ` Christopher Faylor
2011-05-20 18:30             ` Chris Sutcliffe
2011-05-20 18:45               ` Chris Sutcliffe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110520054420.GA17408@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).