Brian Ford wrote:
On Mon, 29 Mar 2004, Andy Rushton wrote:
The really odd thing is that I have another PC at home with the same
version of XP, same update status and as far as I can tell, the same
install of Cygwin and I have no problems.
Are you sure about the same update status part?
-Original Message-
From: cygwin-owner On Behalf Of Andy Rushton
Sent: 07 April 2004 10:36
My computer
here - the
one that was getting the error - is supposed to be on auto-update.
That's what the settings say it is. However, I found that a manual
update found 5 'critical'
Christopher Faylor wrote:
On Sun, Apr 04, 2004 at 12:16:06AM -0500, Mark Blackburn wrote:
Christopher Faylor wrote:
On Fri, Apr 02, 2004 at 08:27:32PM -0500, Mark Blackburn wrote:
Brian Ford wrote:
On Mon, 29 Mar 2004, Mark Blackburn wrote:
No it isn't. I recently tried my own build of
On Tue, 6 Apr 2004, Mark Blackburn wrote:
Christopher Faylor wrote:
configure with --enable-debugging.
I did, I still couldn't get gdb to pop up. In any case its moot for me.
My wife did a windows update on my win2k machine and this problem
doesn't happen any more for the post 1.5.9
On Mon, 29 Mar 2004, Andy Rushton wrote:
I'm having similar problems with release 1.5.9. I thought that if I
posted more information it might help to pin down the problem.
I have just done a complete clean reinstall of Cygwin (i.e. deleted the
directory and registry settings first) using the
On Sun, Apr 04, 2004 at 12:16:06AM -0500, Mark Blackburn wrote:
Christopher Faylor wrote:
On Fri, Apr 02, 2004 at 08:27:32PM -0500, Mark Blackburn wrote:
Brian Ford wrote:
On Mon, 29 Mar 2004, Mark Blackburn wrote:
No it isn't. I recently tried my own build of cygwin:
Could you possibly
Christopher Faylor wrote:
On Fri, Apr 02, 2004 at 08:27:32PM -0500, Mark Blackburn wrote:
Brian Ford wrote:
On Mon, 29 Mar 2004, Mark Blackburn wrote:
No it isn't. I recently tried my own build of cygwin:
Could you possibly build it with the attached patch and report the
strace output? Also,
On Mon, 29 Mar 2004, Mark Blackburn wrote:
No it isn't. I recently tried my own build of cygwin:
Could you possibly build it with the attached patch and report the strace
output? Also, if you could scan cygwin/winsup/cygwin/how-to-debug-cygwin.txt,
it will tell you how to get a working gdb to
On Fri, 2 Apr 2004, Brian Ford wrote:
Could you possibly build it with the attached patch and report the strace
output? Also, if you could scan cygwin/winsup/cygwin/how-to-debug-cygwin.txt,
it will tell you how to get a working gdb to debug this. The output of
info dll would be interesting.
Brian Ford wrote:
On Mon, 29 Mar 2004, Mark Blackburn wrote:
No it isn't. I recently tried my own build of cygwin:
Could you possibly build it with the attached patch and report the strace
output? Also, if you could scan cygwin/winsup/cygwin/how-to-debug-cygwin.txt,
it will tell you how to
On Fri, Apr 02, 2004 at 08:27:32PM -0500, Mark Blackburn wrote:
Brian Ford wrote:
On Mon, 29 Mar 2004, Mark Blackburn wrote:
No it isn't. I recently tried my own build of cygwin:
Could you possibly build it with the attached patch and report the
strace output? Also, if you could scan
I'm having similar problems with release 1.5.9. I thought that if I
posted more information it might help to pin down the problem.
I have just done a complete clean reinstall of Cygwin (i.e. deleted the
directory and registry settings first) using the net installer and
therefore using the
My problems with chgrp -R from coreutils are fixed with this snapshot.
However I'm seeing some other problems:
[EMAIL PROTECTED] ~
$ cygstart .
7 [main] ? 760 cygheap_fixup_in_child: Couldn't reserve space for
cygwin's heap (0x616B 0x41) in child, Win32 error 487
At 06:17 PM 3/26/2004, you wrote:
My problems with chgrp -R from coreutils are fixed with this snapshot. However I'm
seeing some other problems:
[EMAIL PROTECTED] ~
$ cygstart .
7 [main] ? 760 cygheap_fixup_in_child: Couldn't reserve space for cygwin's heap
(0x616B 0x41) in child,
14 matches
Mail list logo
