From: Mike Dahmus <mdahmus@potomacfusion.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Repeated problems with svn even after rebaseall and peflagsall on Windows 7
Date: Tue, 17 May 2011 00:27:00 -0000 [thread overview]
Message-ID: <688D8B269DCBDE44A466DC43D403624C0155C32550@pfi-mail> (raw)
i.e.:
mdahmus@MikeDahmus-PC /pfisvn/DCGS/trunk
$ svn up
0 [main] svn 9484 C:\cygwin\bin\svn.exe: *** fatal error - unable to remap
\\?\C:\cygwin\lib\sasl2\cygdigestmd5-2.dll to same address as parent: 0x830000
!= 0xA50000
Stack trace:
Frame Function Args
0028B188 6102796B (0028B188, 00000000, 00000000, 00000000)
0028B478 6102796B (6117EC60, 00008000, 00000000, 61180977)
0028C4A8 61004F1B (611A7FAC, 612485B4, 00830000, 00A50000)
End of stack trace
1 [main] svn 8864 fork: child 9484 - died waiting for dll loading, errno 1
1
svn: Can't create tunnel: Resource temporarily unavailable
mdahmus@MikeDahmus-PC /pfisvn/DCGS/trunk
$ svn up
0 [main] svn 8696 exception::handle: Exception: STATUS_ACCESS_VIOLATION
17623 [main] svn 8696 open_stackdumpfile: Dumping stack trace to svn.exe.stack
dump
0 [main] svn 5304 exception::handle: Exception: STATUS_ACCESS_VIOLATION
720 [main] svn 5304 open_stackdumpfile: Dumping stack trace to svn.exe.stack
dump
0 [main] svn 9616 exception::handle: Exception: STATUS_ACCESS_VIOLATION
885 [main] svn 9616 open_stackdumpfile: Dumping stack trace to svn.exe.stack
dump
0 [main] svn 7708 exception::handle: Exception: STATUS_ACCESS_VIOLATION
882 [main] svn 7708 open_stackdumpfile: Dumping stack trace to svn.exe.stack
dump
0 [main] svn 4020 exception::handle: Exception: STATUS_ACCESS_VIOLATION
813 [main] svn 4020 open_stackdumpfile: Dumping stack trace to svn.exe.stack
dump
0 [main] svn 8884 exception::handle: Exception: STATUS_ACCESS_VIOLATION
1687 [main] svn 8884 open_stackdumpfile: Dumping stack trace to svn.exe.stack
dump
1 [main] svn 3916 fork: child -1 - died waiting for longjmp before initial
ization, retry 0, exit code 0x600, errno 11
Happening more and more often, even after I run rebaseall and peflagsall. Any ideas? This is rapidly becoming unusable. On an older system, a rebaseall would usually fix this problem for at least a couple of months; now I'm lucky if it has any effect at all.
Have spent much time the last month or so googling this to little avail. The opinion of the internet seems to be that this isn't a real problem. My grey hair would beg to disagree.
Regards,
Mike Dahmus
mdahmus@potomacfusion.com
--
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 reply other threads:[~2011-05-17 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 0:27 Mike Dahmus [this message]
2011-05-17 1:11 ` Christopher Faylor
2011-05-19 15:26 ` Mike Dahmus
2011-05-19 15:32 ` Larry Hall (Cygwin)
2011-05-19 15:39 ` Christopher Faylor
2011-05-19 15:55 ` Larry Hall (Cygwin)
2011-05-19 19:12 ` Mike Dahmus
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=688D8B269DCBDE44A466DC43D403624C0155C32550@pfi-mail \
--to=mdahmus@potomacfusion.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).