On Fri, Aug 14, 2009 at 12:15:57PM +0200, Reini Urban wrote:
>Fixed with cygwin-1.7.0-58, the perl suite runs through now.
>
>Thanks, esp. thanks to Peter Rosin.
All thanks for this fix go to Corinna. I was in the middle of
tracking this down when she sent her first patch to rectify
the problem.
2009/8/4 Christopher Faylor:
> On Tue, Aug 04, 2009 at 09:06:00PM +0200, Reini Urban wrote:
>>2009/8/4 Christopher Faylor:
>>> On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
2009/8/4 Christopher Faylor:
>On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
>>
On 03/08/2009 23:53, Christopher Faylor wrote:
Well, at least this time there was cygcheck output. However, other than
showing that you're running Windows 7, I don't see anything too useful.
So, it looks likely that who reports a bug is going to be SOL unless
you can show me how to duplicate the
On Tue, Aug 04, 2009 at 09:06:00PM +0200, Reini Urban wrote:
>2009/8/4 Christopher Faylor:
>> On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
>>>2009/8/4 Christopher Faylor:
On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
>On 01/08/2009 15:10, Christopher Fay
2009/8/4 Christopher Faylor:
> On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
>>2009/8/4 Christopher Faylor:
>>>On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
On 01/08/2009 15:10, Christopher Faylor wrote:
>I have uploaded a new Cygwin 1.7 test release, 1.7
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
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
On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
>2009/8/4 Christopher Faylor:
>>On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
>>>On 01/08/2009 15:10, Christopher Faylor wrote:
I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
This fixes the bug
2009/8/4 Christopher Faylor:
> On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
>>On 01/08/2009 15:10, Christopher Faylor wrote:
>>> I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
>>>
>>> This fixes the bug introduced in -53 and -54 which resulted in various
>>> problems
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.
On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
>On 01/08/2009 15:10, Christopher Faylor wrote:
>> I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
>>
>> This fixes the bug introduced in -53 and -54 which resulted in various
>> problems execing programs as seen here:
>
>I
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. Now in a DOS window, when I try to start TCSH, I
>>get:
>>
>>f:\>tcsh
On 08/03/2009 11:42 PM, 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. Now in a DOS window, when I try to start TCSH, I
get:
f:\>tcsh
3 [main] tcsh 6028 _
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. Now in a DOS window, when I try to start TCSH, I
>get:
>
>f:\>tcsh
> 3 [main] tcsh 6028 _cygtls::handle_exceptions: Exception:
>STATUS_A
On Tue, Aug 04, 2009 at 11:24:40AM +0800, Huang Bambo wrote:
>Try release 51, it's the last stable version for me.
Yes. We got that.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Uns
On Tue, Aug 04, 2009 at 11:21:21AM +0800, Huang Bambo wrote:
>I confirm this problem.
>After ls command can't list anything, command "strace ls" will work
>with correct result.
You really do need to check out http://cygwin.com/problems.html . In
particular, the cygcheck output mentioned there wou
Try release 51, it's the last stable version for me.
2009/8/4 Jim Reisert AD1C :
> I removed the *56* release file from my Cygwin install directory and
> tried a re-install. Now in a DOS window, when I try to start TCSH, I
> get:
>
> f:\>tcsh
> 3 [main] tcsh 6028 _cygtls::handle_exceptions:
I removed the *56* release file from my Cygwin install directory and
tried a re-install. Now in a DOS window, when I try to start TCSH, I
get:
f:\>tcsh
3 [main] tcsh 6028 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
502 [main] tcsh 6028 open_stackdumpfile: Dumping stac
I confirm this problem.
After ls command can't list anything, command "strace ls" will work
with correct result.
2009/8/4 Jim Reisert AD1C :
> I did NOT have the problem on my work PC. I do have the problem on my
> home PC (even after rebooting). Home is running Wnidows SP3, work is
> running Wi
I did NOT have the problem on my work PC. I do have the problem on my
home PC (even after rebooting). Home is running Wnidows SP3, work is
running Windows SP2 (I think).
- Jim
On Sun, Aug 2, 2009 at 9:45 AM, Jim Reisert AD1C wrote:
> It's worse than that.
>
> In an xterm, the first "ls" works (
I forced a REINSTALL of cygwin1.dll and this time it downloaded the
correct version. Everything is fine now.
Christopher Faylor wrote:
On Sun, Aug 02, 2009 at 05:15:33PM -0400, Paul McFerrin wrote:
Folks. Try again with updating 1.7-56. When it is downloaded from
mirror: mirror.nyi.net,
On Sun, Aug 02, 2009 at 03:26:51PM -0400, Christopher Faylor wrote:
>On Sun, Aug 02, 2009 at 09:03:00PM +0200, Fr??d??ric Bron wrote:
>>> It's worse than that.
>>>
>>> In an xterm, the first "ls" works (I get output) but then nothing
>>> works after that. ??Just get command prompt returned.
>>
>>Sa
On Sun, Aug 02, 2009 at 05:15:33PM -0400, Paul McFerrin wrote:
>Folks. Try again with updating 1.7-56. When it is downloaded from
>mirror: mirror.nyi.net, my 1.7 instance of cygwin will nolonger come up!!
>
>Using my 1.5 instance, and the strings command, I check the 1.7.0-56
>version of cygwi
Folks. Try again with updating 1.7-56. When it is downloaded from
mirror: mirror.nyi.net, my 1.7 instance of cygwin will nolonger come up!!
Using my 1.5 instance, and the strings command, I check the 1.7.0-56
version of cygwin1.dll and it comes up with:
/ext/build/netrel/src/cygwin-1.7.0
On Sun, Aug 02, 2009 at 09:03:00PM +0200, Fr??d??ric Bron wrote:
>> It's worse than that.
>>
>> In an xterm, the first "ls" works (I get output) but then nothing
>> works after that. ??Just get command prompt returned.
>
>Same issue with rxvt. Not only ls, but also vi, cat...
http://cygwin.com/ml/
> It's worse than that.
>
> In an xterm, the first "ls" works (I get output) but then nothing
> works after that. Just get command prompt returned.
Same issue with rxvt. Not only ls, but also vi, cat...
Frédéric
--
Problem reports: http://cygwin.com/problems.html
FAQ: ht
On Sun, Aug 02, 2009 at 09:45:56AM -0600, Jim Reisert AD1C wrote:
>It's worse than that.
>
>In an xterm, the first "ls" works (I get output) but then nothing
>works after that. Just get command prompt returned.
Can't duplicate this or the emacs problem. Sorry.
cgf
--
Problem reports: htt
I'm running cygwin-1.7.0-56 and I've no problem with xterm. After the first ls,
I can enter other commands too.
I don;t use emacs. But I can start emacs and xemacs and get into editing the
file. Both xterm and emacs do not come back with a prompt.
Eric.
--
Problem reports: http://cygwin.c
It's worse than that.
In an xterm, the first "ls" works (I get output) but then nothing
works after that. Just get command prompt returned.
- Jim
On Sun, Aug 2, 2009 at 9:41 AM, Jim Reisert AD1C wrote:
> Emacs no longer works. It comes back to the prompt, no window.
>
> Using latest X-org and
Emacs no longer works. It comes back to the prompt, no window.
Using latest X-org and Emacs.
- Jim
On Sat, Aug 1, 2009 at 2:10 PM, Christopher
Faylor wrote:
> I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
>
> This fixes the bug introduced in -53 and -54 which resulted in various
> pr
No obvious problems with this release - thanks!
On 8/1/2009 2:10 PM, Christopher Faylor wrote:
I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
This fixes the bug introduced in -53 and -54 which resulted in various
problems execing programs as seen here:
http://cygwin.com/ml/cygwin/20
I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
This fixes the bug introduced in -53 and -54 which resulted in various
problems execing programs as seen here:
http://cygwin.com/ml/cygwin/2009-07/msg01057.html
http://cygwin.com/ml/cygwin/2009-07/msg01060.html
http://cygwin.com/ml/cygwin/2
32 matches
Mail list logo
