Re: Intermittent failures with ctrl-c

2013-01-18 Thread Christopher Faylor
than false. I'm investigating now. > >I noticed that you checked in some additional changes on the 16th that >look related to this, so I tested again with today's snapshot (20130118). I thought I sent a "try a snapshot" but I must have been hallucinating again. >I

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Christopher Faylor
On Fri, Jan 18, 2013 at 04:10:25PM -0500, Christopher Faylor wrote: >On Sat, Jan 19, 2013 at 12:18:39AM +0400, Andrey Repin wrote: >>Greetings, Corinna Vinschen! >> I saw that you made another change to this function. Is it possible that this might actually fix the "rtorrent problem"? >>

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Christopher Faylor
On Sat, Jan 19, 2013 at 12:18:39AM +0400, Andrey Repin wrote: >Greetings, Corinna Vinschen! > >>> I saw that you made another change to this function. Is it possible that >>> this might actually fix the "rtorrent problem"? > >> No. It only adds the MS_SYNC handling. rtorrent uses MS_ASYNC. > >Th

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Andrey Repin
Greetings, Corinna Vinschen! >> I saw that you made another change to this function. Is it possible that >> this might actually fix the "rtorrent problem"? > No. It only adds the MS_SYNC handling. rtorrent uses MS_ASYNC. That made me think... If rtorrent uses MS_ASYNC, shouldn't *rtorrent* be

Re: Intermittent failures with ctrl-c

2013-01-18 Thread Tom Honermann
changes on the 16th that look related to this, so I tested again with today's snapshot (20130118). I was still able to produce hangs using the same test case. The symptoms are slightly different than I had seen previously. bash hung 2 out of the ~60 times I interrupted the test. No

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Christopher Faylor
On Fri, Jan 18, 2013 at 05:07:42PM +0100, Corinna Vinschen wrote: >Current binutils CVS HEAD doesn't build on Cygwin(*). The 2.23.1 >version should work, though. I have a number of weird problems building binutils that will take some time to track down. cgf -- Problem reports: http://cygw

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Corinna Vinschen
On Jan 18 10:43, Christopher Faylor wrote: > On Fri, Jan 18, 2013 at 10:32:05AM +0100, Corinna Vinschen wrote: > >On Jan 17 19:35, Christopher Faylor wrote: > >> And, Corinna, please if the change I made to your function is wrong or > >> you just don't like my variable names or comments please feel

Re: Binutils objcopy bug (was Re: rebase segfault)

2013-01-18 Thread Christopher Faylor
On Fri, Jan 18, 2013 at 04:34:25PM +0100, marco atzeri wrote: >On 1/16/2013 1:35 PM, Corinna Vinschen wrote: >> >> As far as I can tell it's an objcopy bug. >> >> The stripped version of the DLL has a normal relocation information >> which at one point ends in a NULL IMAGE_BASE_RELOCATION record, a

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Christopher Faylor
On Fri, Jan 18, 2013 at 10:32:05AM +0100, Corinna Vinschen wrote: >On Jan 17 19:35, Christopher Faylor wrote: >> And, Corinna, please if the change I made to your function is wrong or >> you just don't like my variable names or comments please feel free to >> expunge what I did with extreme prejudi

Re: Binutils objcopy bug (was Re: rebase segfault)

2013-01-18 Thread marco atzeri
On 1/16/2013 1:35 PM, Corinna Vinschen wrote: As far as I can tell it's an objcopy bug. The stripped version of the DLL has a normal relocation information which at one point ends in a NULL IMAGE_BASE_RELOCATION record, as expected. After calling `objcopy --add-gnu-debuglink', the relocation i

Re: rtorrent and recent snapshots - apparent problem with msync()

2013-01-18 Thread Corinna Vinschen
On Jan 17 19:35, Christopher Faylor wrote: > On Thu, Jan 17, 2013 at 04:42:36PM -0500, Chris Sutcliffe wrote: > >On 17 January 2013 06:55, Chris Sutcliffe wrote: > >> On 17 January 2013 01:24, Christopher Faylor wrote: > >>> Is there a stackdump file? If not, I guess if you could make a strace > >