Christopher Faylor cgf-use-the-mailinglist-please at cygwin.com writes:
The latest snapshot has some more signal-handling restructuring.
I'd appreciate it if people would check it out.
Looks good so far. I've had a compile that would pretty often lock up cmake
during the config phase so that
The latest snapshot has some more signal-handling restructuring.
I'd appreciate it if people would check it out.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On Wed, Apr 10, 2013 at 09:20:26AM -0400, Christopher Faylor wrote:
The latest snapshot has some more signal-handling restructuring.
I'd appreciate it if people would check it out.
http://cygwin.com/snapshots/
--
Problem reports: http://cygwin.com/problems.html
FAQ:
fairly substantial changes to the
pipe handling so this needs some serious testing, especially on
different platforms, e.g., XP, XP64, Windows 2008, etc.
Please try the latest snapshot at:
http://cygwin.com/snapshots/
cgf
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ
Christopher Faylor wrote:
Corinna identified a couple of problems and checked in some fixes
which may solve the problem with ssh-add hanging.
Please try the latest snapshot and report success for failure here.
http://cygwin.com/snapshots/
cgf
Seems to have fixed the problem. Thanks
On Thu, Mar 10, 2005 at 08:24:25AM -0500, Chuck wrote:
Christopher Faylor wrote:
Corinna identified a couple of problems and checked in some fixes which
may solve the problem with ssh-add hanging.
Please try the latest snapshot and report success for failure here.
http://cygwin.com/snapshots
Hi All...
With the latest snapshot, I can not see the problem now.
It also seemd to take a long time sometimes with the previous snapshot
(March 4) in ssh-add. That also seems better now. But I really don't have
enough data to say much here...it just seems better.
Thanks,
...Karl
--
On Thu, Mar 10, 2005 at 08:24:25AM -0500, Chuck wrote:
Christopher Faylor wrote:
Corinna identified a couple of problems and checked in some fixes which
may solve the problem with ssh-add hanging.
Please try the latest snapshot and report success for failure here.
http://cygwin.com
Hi All...
With the latest snapshot, I can not see the problem now.
It also seemd to take a long time sometimes with the previous snapshot
(March 4) in ssh-add. That also seems better now. But I really don't have
enough data to say much here...it just seems better.
You're right-- after
Corinna identified a couple of problems and checked in some fixes
which may solve the problem with ssh-add hanging.
Please try the latest snapshot and report success for failure here.
http://cygwin.com/snapshots/
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
Hi,
This snapshot (20040306) fixes some of the problems with running emacs.
The problem existed even with snapshot of 20040225 (hadn't tried 0305).
emacs (under X11) has been running fine for over a day now.
It used to crash randomly (SEGV), earlier.
Thanks,
rb
Christopher Faylor wrote:
The
The latest snapshot should fix virtual memory exhausted errors that
were reported when running make -j.
I am close to releasing cygwin 1.5.8 so I want to verify that this is
fixed.
http://cygwin.com/snapshots/
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
Christopher Faylor wrote:
The latest snapshot should fix virtual memory exhausted errors that
were reported when running make -j.
I am close to releasing cygwin 1.5.8 so I want to verify that this is
fixed.
OK, did that, and got a freeze after 196 iterations. Still using your
make with debug info.
Volker Quetschke wrote:
Christopher Faylor wrote:
The latest snapshot should fix virtual memory exhausted errors that
were reported when running make -j.
I am close to releasing cygwin 1.5.8 so I want to verify that this is
fixed.
OK, did that, and got a freeze after 196 iterations. Still using
OK, did that, and got a freeze after 196 iterations. Still using your
make with debug info.
This time my script enabled the malloc debug info
strace -mall+malloc -o strace.out make -j -f MakefileV $logname 2
$logerr
so the strace is very long, you can find it here:
Christopher Faylor wrote:
I fixed some more problems with both vfork and with fork recently. The
fixes are currently in cvs.
It's much better.
CYGWIN_ME-4.90 hpn5170x 1.5.6(0.108/3/2) 2003-12-29 22:44 i686 unknown
unknown Cygwin
I only have problems with the more complicated tests.
Open two
On Sun, Dec 28, 2003 at 12:26:32PM -0500, Nicholas Wourms wrote:
Pierre A. Humblet wrote:
At 12:46 PM 12/27/2003 -0500, Christopher Faylor wrote:
I missed the 'sh -c' clue in your previous message. Since sh uses
vfork, that indicates a vfork problem. I've checked in some more
changes to deal
On Sat, Dec 27, 2003 at 06:28:09PM -0500, Pierre A. Humblet wrote:
...when I launch inetd from an rxvt window running bash, or from a Dos
window running cygwin.bat with tty, I still see tty handles in inetd.
I fixed some more problems with both vfork and with fork recently. The
fixes are
On Mon, Dec 29, 2003 at 10:04:01PM -0500, Christopher Faylor wrote:
On Sun, Dec 28, 2003 at 12:26:32PM -0500, Nicholas Wourms wrote:
Pierre A. Humblet wrote:
At 12:46 PM 12/27/2003 -0500, Christopher Faylor wrote:
I missed the 'sh -c' clue in your previous message. Since sh uses
vfork, that
Pierre A. Humblet wrote:
At 12:46 PM 12/27/2003 -0500, Christopher Faylor wrote:
I missed the 'sh -c' clue in your previous message. Since sh uses
vfork, that indicates a vfork problem. I've checked in some more
changes to deal with this. It seems to do the right thing both with sh
-c and
Christopher Faylor wrote:
On Fri, Dec 26, 2003 at 05:37:36PM +0100, Philippe Torche wrote:
Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
I've tested it (CVS version 12:35 GMT + 1) on our 4 Xeon on W2003S and
unfortunately my
On Sat, Dec 27, 2003 at 05:29:56PM +0100, Philippe Torche wrote:
So, if you were just reporting this as a data point, then thanks. If
you are expecting me to do something about it, then, you will,
unfortunately, be disappointed.
:-( Not you but other maybe !
Ok. I'll just ignore your periodic
On Fri, Dec 26, 2003 at 10:27:51PM -0500, Pierre A. Humblet wrote:
At 09:40 PM 12/26/2003 -0500, Christopher Faylor wrote:
I tried the current CVS version and I don't see any stray tty garbage
with inetd. I never tried this with an older snapshot, however, so I
don't know if I would have been
At 12:46 PM 12/27/2003 -0500, Christopher Faylor wrote:
I missed the 'sh -c' clue in your previous message. Since sh uses
vfork, that indicates a vfork problem. I've checked in some more
changes to deal with this. It seems to do the right thing both with sh
-c and without. It also should have
Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
cgf
I've tested it (CVS version 12:35 GMT + 1) on our 4 Xeon on W2003S and
unfortunately my previous test case (run_t.sh and t.sh) always fails.
The test suite runs soon happily
Christopher == Christopher Faylor [EMAIL PROTECTED] writes:
Christopher The subject says it all.
Christopher I'm hoping to release cygwin 1.5.6 shortly after Christmas.
I just checked cygwin1-20031225
Apache (1.3.24-5) stackdumps right away and wmaker (0.80.0-2) reproducable
after 5
On Wed, Dec 24, 2003 at 06:27:59PM -0500, Christopher Faylor wrote:
On Wed, Dec 24, 2003 at 06:15:24PM -0500, Pierre A. Humblet wrote:
At 11:59 AM 12/24/2003 -0500, Christopher Faylor wrote:
On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote:
On Tue, Dec 23, 2003 at 05:28:16PM
On Fri, Dec 26, 2003 at 03:46:41PM -0500, Pierre A. Humblet wrote:
On Wed, Dec 24, 2003 at 06:27:59PM -0500, Christopher Faylor wrote:
On Wed, Dec 24, 2003 at 06:15:24PM -0500, Pierre A. Humblet wrote:
At 11:59 AM 12/24/2003 -0500, Christopher Faylor wrote:
On Wed, Dec 24, 2003 at 10:29:51AM
At 05:59 PM 12/26/2003 -0500, Christopher Faylor wrote:
I added strace debugging. You can use that as a clue for what I was
talking about and make it visible if you can't run exim under strace.
I put a try_to_debug(1). Waiting for something to happen.
Also, while running sysinternals I
On Fri, Dec 26, 2003 at 05:59:59PM -0500, Christopher Faylor wrote:
On Fri, Dec 26, 2003 at 03:46:41PM -0500, Pierre A. Humblet wrote:
Also, while running sysinternals I noticed to the exim daemon still had
tty related handles, despite setsid(). Ditto for inetd.
Calling setsid does not
On Fri, Dec 26, 2003 at 09:13:36PM -0500, Pierre A. Humblet wrote:
At 05:59 PM 12/26/2003 -0500, Christopher Faylor wrote:
I added strace debugging. You can use that as a clue for what I was
talking about and make it visible if you can't run exim under strace.
I put a try_to_debug(1). Waiting
On Fri, Dec 26, 2003 at 09:40:10PM -0500, Christopher Faylor wrote:
On Fri, Dec 26, 2003 at 09:13:36PM -0500, Pierre A. Humblet wrote:
At 05:59 PM 12/26/2003 -0500, Christopher Faylor wrote:
I added strace debugging. You can use that as a clue for what I was
talking about and make it visible
At 09:40 PM 12/26/2003 -0500, Christopher Faylor wrote:
I tried the current CVS version and I don't see any stray tty garbage
with inetd. I never tried this with an older snapshot, however, so I
don't know if I would have been lucky before. I did try a much simpler
test case which worked
On Thu, Dec 25, 2003 at 04:05:24PM +0930, Trevor Forbes wrote:
I run the testsuite when I built the dll which gives:
FAIL: msgtest.c (execute)
FAIL: semtest.c (execute)
FAIL: shmtest.c (execute)
FAIL: pthread/mainthreadexits.c (execute)
I think we've already been down the testsuite route.
The
On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
On WinMe the queue runner forked by the exim daemon still occasionally
produces a popup indicating an error in Cygwin1.dll
In addition
On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote:
On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
On WinMe the queue runner forked by the exim daemon still occasionally
At 11:59 AM 12/24/2003 -0500, you wrote:
On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote:
On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
On WinMe the queue runner forked
On Wed, Dec 24, 2003 at 04:20:37PM -0500, Pierre A. Humblet wrote:
At 11:59 AM 12/24/2003 -0500, you wrote:
On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote:
On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin
At 11:59 AM 12/24/2003 -0500, Christopher Faylor wrote:
On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote:
On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
On WinMe the
Using a CVS Head version, I get a popup with:
The instruction at 0x61085fba referenced memory at 0x61002f90. The
memory could not be written
$ addr2line -e /bin/cygwin1.dll 61085fba
/src/cygwin/obj/obj-org/i686-pc-cygwin/winsup/cygwin/../../../../../src/
winsup/cygwin/shm.cc:331
/* Try
On Thu, Dec 25, 2003 at 09:07:51AM +0930, Trevor Forbes wrote:
Using a CVS Head version, I get a popup with:
The instruction at 0x61085fba referenced memory at 0x61002f90. The
memory could not be written
$ addr2line -e /bin/cygwin1.dll 61085fba
I was running the open_posix_testsuite against the current homebuilt
cygwin1.dll but I get the same error if I use the new dll to build
itself. It only happens randomly to gcc.exe but it always errors at the
same location 0x61085fba.
I run the testsuite when I built the dll which gives:
FAIL:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
On Tue, 23 Dec 2003, Christopher Faylor wrote:
The subject says it all.
I'm hoping to release cygwin 1.5.6 shortly after Christmas.
Have you run the testsuite lately? I get a heap of failures on NT4. But,
in that timeframe, I certainly won't have time to look at them.
lots of child process
On Tue, Dec 23, 2003 at 04:39:13PM -0600, Brian Ford wrote:
Have you run the testsuite lately? I get a heap of failures on NT4.
But, in that timeframe, I certainly won't have time to look at them.
You can safely assume that cygwin is not released without my running the
test suite.
I haven't run
On Tue, 23 Dec 2003, Christopher Faylor wrote:
On Tue, Dec 23, 2003 at 04:39:13PM -0600, Brian Ford wrote:
Have you run the testsuite lately? I get a heap of failures on NT4.
But, in that timeframe, I certainly won't have time to look at them.
You can safely assume that cygwin is not
On Tue, Dec 23, 2003 at 04:45:27PM -0600, Brian Ford wrote:
On Tue, 23 Dec 2003, Christopher Faylor wrote:
On Tue, Dec 23, 2003 at 04:39:13PM -0600, Brian Ford wrote:
Have you run the testsuite lately? I get a heap of failures on NT4.
But, in that timeframe, I certainly won't have time to
Christopher Faylor wrote:
The latest snapshot should fix some /etc handling problems (thanks to
ideas and code from Pierre Humblet), like the dreaded BSOD. It may also
solve the pipes are slow problem. There are also all of the fixes
accumulated since 1.3.18, of course.
Indeed it does seem to
Chris,
On Fri, Jan 17, 2003 at 12:52:16AM -0500, Christopher Faylor wrote:
If I don't hear too many whines about this snapshot, it may become
1.3.19.
The 2003-Jan-17 snapshot seems to fix the symlink problem that I
mentioned in:
http://cygwin.com/ml/cygwin/2003-01/msg00827.html
However,
Dan Holmsand wrote:
Indeed it does seem to stop the BSODding on my machines. Thanks!
Still no BSOD.
However, now I'm having trouble with postgresql: the postmaster dies as
soon as I exit psql. Reverting to a cygwin1.dll built from cvs from four
days ago fixes the problem.
Here is what the
cgf == Christopher Faylor [EMAIL PROTECTED] writes:
cgf The latest snapshot should fix some /etc handling problems
cgf (thanks to ideas and code from Pierre Humblet), like the
cgf dreaded BSOD.
Where can I read more about that BSOD problem? I'm getting
blue-screens myself and would
On Fri, Jan 17, 2003 at 10:44:55AM -0500, Jason Tishler wrote:
Chris,
On Fri, Jan 17, 2003 at 12:52:16AM -0500, Christopher Faylor wrote:
If I don't hear too many whines about this snapshot, it may become
1.3.19.
The 2003-Jan-17 snapshot seems to fix the symlink problem that I
mentioned in:
Chris,
On Fri, Jan 17, 2003 at 02:03:53PM -0500, Christopher Faylor wrote:
This should be fixed now. It was a simple mistake, as far as I could
tell. How does the refreshed snapshot look?
Looking good!
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
On Fri, Jan 17, 2003 at 12:52:16AM -0500, you [Christopher Faylor] wrote:
The latest snapshot should fix some /etc handling problems (thanks to
ideas and code from Pierre Humblet), like the dreaded BSOD. It may also
solve the pipes are slow problem. There are also all of the fixes
Chris,
On Fri, Jan 17, 2003 at 02:49:24PM -0500, Jason Tishler wrote:
On Fri, Jan 17, 2003 at 02:03:53PM -0500, Christopher Faylor wrote:
This should be fixed now. It was a simple mistake, as far as I
could tell. How does the refreshed snapshot look?
Looking good!
I spoke too soon.
The latest 1-17 snapshot fixes the pipe problem for me. No other
problems detected so far. Thanks!
Christopher Faylor wrote:
The latest snapshot should fix some /etc handling problems (thanks to
ideas and code from Pierre Humblet), like the dreaded BSOD. It may also
solve the pipes are
I am encountering sporadic segmentation faults from tools like ls and
find. Specifically, I was invoking find as a child process from Cygwin
XEmacs, and it was getting a segmentation fault at different locations
in my (somewhat deep) directory structure.
After this started to occur, I started an
On Fri, Jan 17, 2003 at 04:17:27PM -0500, Jason Tishler wrote:
Chris,
On Fri, Jan 17, 2003 at 02:49:24PM -0500, Jason Tishler wrote:
On Fri, Jan 17, 2003 at 02:03:53PM -0500, Christopher Faylor wrote:
This should be fixed now. It was a simple mistake, as far as I
could tell. How does the
On Fri, Jan 17, 2003 at 08:04:43PM -0500, Christopher Faylor wrote:
On Fri, Jan 17, 2003 at 04:17:27PM -0500, Jason Tishler wrote:
Chris,
On Fri, Jan 17, 2003 at 02:49:24PM -0500, Jason Tishler wrote:
On Fri, Jan 17, 2003 at 02:03:53PM -0500, Christopher Faylor wrote:
This should be fixed now.
It works. I can now proceed with my progrect(Making music with Cygwin,
EZPNO, and Timidity++
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Christopher Faylor
Sent: Friday, January 17, 2003 9:39 PM
To: [EMAIL PROTECTED]
Subject: Re: please try the latest
It does fix the slow pipes on my machine when seti@home is running.
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 17, 2003 4:52 PM
Subject: please try the latest snapshot
The latest snapshot should fix some /etc handling
On Fri, Jan 17, 2003 at 05:54:57PM +1100, Eugene Rosenzweig wrote:
It does fix the slow pipes on my machine when seti@home is running.
Ok, thanks.
If this is true to form, the next message will be from someone who
indicates that the snapshot either shows no change or makes things
worse.
cgf
--
62 matches
Mail list logo
