Displaying 5 results from an estimated 5 matches similar to: "rsync 2.6.3 hang (was rsync 2.6.2 crash)"
2010 Jan 10
1
cygwin 1.7.x rsync 3.0.6 hangs at arbitrary reproducible points in transfers
Since upgrading to cygwin 1.7.x, I'm unable to complete rsync jobs to a
Debian machine (running stable). cygwin rsync is 3.0.6; Debian is 3.0.3.
The transfer goes for a while and then just gets stuck halfway through
an arbitrary file. If I cancel and restart, same thing (but gets a
little further). If I manually copy the file in question, it will
usually go a bit longer and then get stuck
2003 Jul 20
1
rsync on cygwin is hanging
I am trying to backup a Windows machine to a Linux machine using rsync
(over ssh).
I have been able to successfully sync a few files at a time, but when I
try to backup an entire tree the process hangs on both machines.
I believe this is a different problem than one posted on here before,
but I did try this patch with no success:
2013 Jan 07
1
[LLVMdev] Need to create symbols only once
Hi Nick,
On 12/7/2012 4:59 PM, Nick Kledzik wrote:
>
> We have a similar requirement in darwin's ld64 linker, but even more general. Any binary can do the following to introspect itself:
>
> struct stuff { int a; int b; };
>
> extern struct stuff* stuff_start __asm("section$start$__DATA$__my");
> extern struct stuff* stuff_end
2012 Dec 10
1
[LLVMdev] Need to create symbols only once
Thanks for the reply Nick.
I will use the Writer::addFiles functionality. Do you want to move the
SimpleFile class to lld/Core ?
It might be useful for other types of object files too(like for ELF here).
How does typeFirstInSection/typeLastinSection know that the addresses
that need to be used for those symbols are the symbol values for the
section start / section end ?
I didnt see
2012 Dec 07
0
[LLVMdev] Need to create symbols only once
On Dec 7, 2012, at 11:51 AM, Shankar Easwaran wrote:
> We have few symbols like __bss_start, __bss_end, which are Undefined symbols in the code.
>
> I want a way in the Reader to create specific atoms before the linker bootstraps.
>
> I didnt find a way to do that with the existing interfaces.
>
> The way it needs to work is as below :-
>
> 1) ReaderELF creates