From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Continued rsync failures
Date: Sat, 8 May 2021 15:36:18 -0400 [thread overview]
Message-ID: <77f65021-ad13-5864-6deb-0bf7b2dffb88@cornell.edu> (raw)
In-Reply-To: <430fbe88-f57d-4e65-11cf-96207ee3ee17@pdc.ca>
[Please don't top post on this list.]
On 5/8/2021 11:03 AM, Brent Epp wrote:
> Sorry, my silly mail client doesn't reply to the list by default.
>
> ------------------------------
>
> It might be worth noting that these rsync commands run using an on-demand script
> to manage sync jobs. Generally, it will execute rsync once with `--dry-run` to
> gather a list of files for me to preview:
>
> rsync -avi --progress --no-perms --no-owner --no-group --delete --dry-run -s
> --exclude-from='/cygdrive/d/my/exclusion/file'
> --exclude-from='/cygdrive/d/my/additional/exclusion/file'
> /cygdrive/d/path/to/source'/. '/cygdrive/d/path/to/target'
>
> trace file: http://cygtestdata.ddnsfree.com/strace.exec1.out
>
> Then it can run rsync a consecutive time:
>
> rsync -avi --progress --no-perms --no-owner --no-group --delete -s
> --exclude-from='/cygdrive/d/my/exclusion/file'
> --exclude-from='/cygdrive/d/my/additional/exclusion/file'
> /cygdrive/d/path/to/source'/. '/cygdrive/d/path/to/target'
>
> trace file: http://cygtestdata.ddnsfree.com/strace.exec2.out
After the line "dll_crt0_0: finished dll_crt0_0 initialization" in the trace
files, you can see several additional DLLs loaded, including several from NVIDIA
and one from 0patch, and then the program crashes. This looks to me like BLODA.
Can you uninstall or at least disable something from NVIDIA or 0patch to see
if that fixes the problem?
Ken
next prev parent reply other threads:[~2021-05-08 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 16:43 Brent Epp
2021-05-07 18:09 ` Ken Brown
2021-05-08 15:03 ` Brent Epp
2021-05-08 19:36 ` Ken Brown [this message]
2021-05-09 13:13 ` Mark Hansen
2021-05-07 19:03 ` Marco Atzeri
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=77f65021-ad13-5864-6deb-0bf7b2dffb88@cornell.edu \
--to=kbrown@cornell.edu \
--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).