From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Issues with latest rtorrent under Win7 x64 when attempting to package
Date: Fri, 20 May 2011 16:51:00 -0000 [thread overview]
Message-ID: <BANLkTi=tGpTuFbgCC-XdvHiXUxnv_yn_FA@mail.gmail.com> (raw)
In-Reply-To: <20110520054420.GA17408@ednor.casa.cgf.cx>
On 20 May 2011 01:44, Christopher Faylor wrote:
> On Thu, May 19, 2011 at 10:01:47PM -0400, Chris Sutcliffe wrote:
>>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".
I've tried l *0xnnnn for each of the addresses in the stack dump:
Stack trace:
Frame Function Args
0028C77C 76D51A2C (00000002, 7EFDE000, 00000000, 0000002F)
0028C798 76D54238 (00000002, 0028C7F0, 00000000, 0000002F)
0028C908 610BF0DD (0028CA1C, 0028C980, 0028C960, 0028C940)
0028CA68 610BF7C0 (00000001, 020D9680, 020D96A0, 020D96C0)
0028CAB8 610C3545 (020D79F8, 0000B5F5, 00000000, 020EC060)
0028CD28 00405AA8 (61244184, 00000000, 0028CD68, 61007038)
0028CD68 61007038 (00000000, 0028CDA4, 61006980, 7EFDE000)
End of stack trace
Each time I get:
No source file for address 0xnnnnnn.
I've tried both the Frame and Function addresses.
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
--
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
next prev parent reply other threads:[~2011-05-20 16:51 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
2011-05-20 16:51 ` Chris Sutcliffe [this message]
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='BANLkTi=tGpTuFbgCC-XdvHiXUxnv_yn_FA@mail.gmail.com' \
--to=ir0nh34d@gmail.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).