Christopher Faylor wrote:
> I've made some more signal-related fixes in the latest snapshot.
>
> I was able to duplicate a ping (but who knows if it THE ping problem)
> problem by running my script which kills a ping running in a while (1)
> loop under tcsh. I tweaked the test to use a system in G
The 20120817 snapshot is holding up good so far in my testing. Fingers
crossed... :-)
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwi
I've made some more signal-related fixes in the latest snapshot.
I was able to duplicate a ping (but who knows if it THE ping problem)
problem by running my script which kills a ping running in a while (1)
loop under tcsh. I tweaked the test to use a system in Germany as the
target which seemed t
On Thu, Aug 06, 2009 at 08:01:42PM +0200, Corinna Vinschen wrote:
>On Aug 6 13:04, Christopher Faylor wrote:
>> On Thu, Aug 06, 2009 at 12:45:31PM -0400, Christopher Faylor wrote:
>>>I was, until yesterday, using the McAffee virus checker. I'll try it
>>>again with that turned off.
>
>IIRC from r
On Aug 6 13:04, Christopher Faylor wrote:
> On Thu, Aug 06, 2009 at 12:45:31PM -0400, Christopher Faylor wrote:
> >On Thu, Aug 06, 2009 at 06:37:34PM +0200, Corinna Vinschen wrote:
> >>On Aug 4 18:36, Christopher Faylor wrote:
> >>> On Tue, Aug 04, 2009 at 02:00:42PM -0400, Christopher Faylor wro
On Thu, Aug 06, 2009 at 12:45:31PM -0400, Christopher Faylor wrote:
>On Thu, Aug 06, 2009 at 06:37:34PM +0200, Corinna Vinschen wrote:
>>On Aug 4 18:36, Christopher Faylor wrote:
>>> On Tue, Aug 04, 2009 at 02:00:42PM -0400, Christopher Faylor wrote:
>>> >On Tue, Aug 04, 2009 at 04:30:49PM +,
On Thu, Aug 06, 2009 at 06:37:34PM +0200, Corinna Vinschen wrote:
>On Aug 4 18:36, Christopher Faylor wrote:
>> On Tue, Aug 04, 2009 at 02:00:42PM -0400, Christopher Faylor wrote:
>> >On Tue, Aug 04, 2009 at 04:30:49PM +, Eric Blake wrote:
>> >>> I'm still seeing some weird stuff in the latest
On Aug 4 18:36, Christopher Faylor wrote:
> On Tue, Aug 04, 2009 at 02:00:42PM -0400, Christopher Faylor wrote:
> >On Tue, Aug 04, 2009 at 04:30:49PM +, Eric Blake wrote:
> >>> I'm still seeing some weird stuff in the latest snapshot. This is
> >>> a fresh install, with nothing other than the
On Wed, Aug 05, 2009 at 12:11:58PM +, Eric Blake wrote:
>> >>> $ git clone git://git.sv.gnu.org/libsigsegv.git
>> >>> Initialized empty Git repository in /home/eblake/libsigsegv/.git/
>> >>> fatal: write error (Socket operation on non-socket)
>> >>
>> I tried it and it failed as you indicated.
> >>> $ git clone git://git.sv.gnu.org/libsigsegv.git
> >>> Initialized empty Git repository in /home/eblake/libsigsegv/.git/
> >>> fatal: write error (Socket operation on non-socket)
> >>
> I tried it and it failed as you indicated.
>
> The next snapshot should fix the problem.
Nope - still seei
On 08/04/2009 07:43 PM, Jerry DeLisle wrote:
I tried to bunzip the snapshot and get the following:
~
$ bunzip2.exe cygwin1-20090804.dll.bz2
bunzip2: Data integrity error when decompressing.
Input file = cygwin1-20090804.dll.bz2, output file =
cygwin1-20090804.dll
It is possible that
I tried to bunzip the snapshot and get the following:
~
$ bunzip2.exe cygwin1-20090804.dll.bz2
bunzip2: Data integrity error when decompressing.
Input file = cygwin1-20090804.dll.bz2, output file =
cygwin1-20090804.dll
It is possible that the compressed file(s) have become corrupted.
On Tue, Aug 04, 2009 at 02:00:42PM -0400, Christopher Faylor wrote:
>On Tue, Aug 04, 2009 at 04:30:49PM +, Eric Blake wrote:
>>> I'm still seeing some weird stuff in the latest snapshot. This is
>>> a fresh install, with nothing other than the Base category + git,
>>> and substituting just cyg
On Tue, Aug 04, 2009 at 11:10:07PM +0800, Huang Bambo wrote:
>2009/8/4 Christopher Faylor wrote:
>>Did anyone test this? ?This snapshot fixes some memory corruption
>>introduced by the recent change to reduce the size of some in-memory
>>filename structures.
>
>The ls can't show file problem and v
On Tue, Aug 04, 2009 at 04:30:49PM +, Eric Blake wrote:
>> I'm still seeing some weird stuff in the latest snapshot. This is
>> a fresh install, with nothing other than the Base category + git,
>> and substituting just cygwin1.dll.
>>
>> $ git clone git://git.sv.gnu.org/libsigsegv.git
>> Init
> I'm still seeing some weird stuff in the latest snapshot. This is
> a fresh install, with nothing other than the Base category + git,
> and substituting just cygwin1.dll.
>
> $ git clone git://git.sv.gnu.org/libsigsegv.git
> Initialized empty Git repository in /home/eblake/libsigsegv/.git/
> fa
The ls can't show file problem and vim go back forground problem seems fixed.
2009/8/4 Christopher Faylor
>
> On Tue, Aug 04, 2009 at 12:49:03AM -0400, Christopher Faylor wrote:
> >On Mon, Aug 03, 2009 at 11:42:40PM -0400, Christopher Faylor wrote:
> >>On Mon, Aug 03, 2009 at 09:21:35PM -0600, Ji
> >This should be fixed in the latest snapshot. Please check it out.
> >
> >You just have to replace the dll and nothing else.
> >
> >http://cygwin.com/snapshots/
>
> Did anyone test this? This snapshot fixes some memory corruption
> introduced by the recent change to reduce the size of some in-
On Tue, Aug 04, 2009 at 12:49:03AM -0400, Christopher Faylor wrote:
>On Mon, Aug 03, 2009 at 11:42:40PM -0400, Christopher Faylor wrote:
>>On Mon, Aug 03, 2009 at 09:21:35PM -0600, Jim Reisert AD1C wrote:
>>>I removed the *56* release file from my Cygwin install directory and
>>>tried a re-install.
19 matches
Mail list logo
