From: "Norman Vine" <nhv@cape.com>
To: <cygwin@cygwin.com>
Subject: Re: YA in the "try a snapshot" series (was Re: latest cvs fork problems)
Date: Mon, 21 Oct 2002 15:20:00 -0000 [thread overview]
Message-ID: <0a0f01c27944$56010680$0636ba8c@sfdev3> (raw)
In-Reply-To: <20021021193525.GB19051@redhat.com>
Christopher Faylor writes:
> On Mon, Oct 21, 2002 at 03:03:13PM -0400, Norman Vine wrote:
> >Christopher Faylor writes:
> >
> >> I was able to duplicate Jason's mmap problem with his version of exim
> >> and, so, I think I was also able to fix it.
> >>
> >> The latest snapshot should solve this problem. The hanging problem
that
> >> I mentioned previously seems to be gone, too... or, more likely, it
> >> will manifest itself 10 seconds after I send this email.
> >>
> >> So, try a snapshot. Collect them all. Win valuable prizes.
> >
> >rxvt seems to have a problem with this dll
>
> You're not using the snapshot. You're using a DLL that you built
> yourself, AFAICT.
Yes, apologies for the misinfo but I had a very similar if not the same
problem with the snapshot. And I did a local rebuild to test ahould
have mentioned this.
FYI
A locally built DLL from Oct 15 CVS files did not have this behavior
>
> >a bash shell in a cmd window does not exhibit this
> >
> >< obj is the top level directory in which I just built the Cygwin DLL >
> >
> >Norman
> >
> ><501> obj
> >$ make clean
.....
> >rm -f libiberty.dvi libiberty.info* libiberty.html
> >make[1]: Leaving directory `/src/cygwin2/obj/libiberty'
> > 2194 [main] ? 2076 open_shared: relocating shared object shared(3)
from
> >0xA000000 to 0xC5D0000 on Windows NT
> >Signal 11
>
> The above message is a warning. The signal 11 is a problem. There should
> be a stackdump file. Please decode the addresses with addr2line and
report
> them here.
There is a sed.exe.stackdump however I am unfamiliar with addr2line and
don't know how to use it.
pointers appreciated
Norman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-10-21 20:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 11:28 latest cvs fork problems Rob Napier
2002-10-17 11:41 ` Christopher Faylor
2002-10-18 6:38 ` Jason Tishler
2002-10-18 8:23 ` Christopher Faylor
2002-10-18 8:31 ` Jason Tishler
2002-10-18 18:29 ` Christopher Faylor
2002-10-18 18:59 ` Jason Tishler
2002-10-18 19:25 ` Christopher Faylor
2002-10-18 22:05 ` Christopher Faylor
2002-10-20 19:09 ` YA in the "try a snapshot" series (was Re: latest cvs fork problems) Christopher Faylor
2002-10-21 8:19 ` Jason Tishler
2002-10-21 12:30 ` Norman Vine
2002-10-21 13:55 ` Christopher Faylor
2002-10-21 15:20 ` Norman Vine [this message]
2002-10-21 20:42 ` Norman Vine
2002-10-22 18:41 ` Norman Vine
2002-10-22 19:13 ` snapshots R us Christopher Faylor
2002-10-22 21:57 ` Gary R. Van Sickle
2002-10-23 0:22 ` Christopher Faylor
2002-10-23 0:41 ` Gary R. Van Sickle
2002-10-21 21:46 ` YA in the "try a snapshot" series (was Re: latest cvs fork problems) Gary R. Van Sickle
2002-10-21 22:24 ` Christopher Faylor
2002-10-21 23:23 ` Gary R. Van Sickle
2002-10-22 4:14 ` Roman Belenov
2002-10-22 10:57 ` Jason Tishler
2002-10-18 17:41 ` latest cvs fork problems Jason Tishler
2002-10-21 20:28 YA in the "try a snapshot" series (was Re: latest cvs fork problems) Pierre A. Humblet
2002-10-21 20:33 ` Christopher Faylor
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='0a0f01c27944$56010680$0636ba8c@sfdev3' \
--to=nhv@cape.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).