Christopher Faylor wrote:
On Mon, Oct 21, 2002 at 03:03:13PM -0400, Norman Vine wrote:
Christopher Faylor writes:
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
So, try a snapshot. Collect them all. Win valuable
Christopher Faylor writes:
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The hanging problem that
I mentioned previously seems to be gone, too... or, more likely, it
will
On Mon, Oct 21, 2002 at 03:03:13PM -0400, Norman Vine wrote:
Christopher Faylor writes:
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The hanging problem that
I mentioned
Christopher Faylor writes:
On Mon, Oct 21, 2002 at 03:03:13PM -0400, Norman Vine wrote:
Christopher Faylor writes:
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The
WinMe, dll built from cvs last night.
/obj: uname -a
CYGWIN_ME-4.90 HPN5170X 1.3.14(0.62/3/2) 2002-10-20 21:59 i686 unknown
3 crashes observed, first two under rxvt, windows went away too fast to
read message. Last one was in console.
/obj: make
C:\PROGRAM FILES\CYGWIN\BIN\SH.EXE: *** 1. unable
Try setting the heap_chunk_size back down to 256M.
The stack dump is just the result of the abort in fork.cc which was
caused by the memory error so it isn't very useful. Thanks for decoding
it, though.
cgf
On Mon, Oct 21, 2002 at 09:41:17PM -0400, Pierre A. Humblet wrote:
WinMe, dll built
Norman Vine wrote:
Christopher Faylor writes:
The signal 11 is a problem. There should
be a stackdump file. Please decode the addresses with addr2line and
report
them here.
$ addr2line -e /bin/cygwin1.dll -f 0x61088F0F 0x61088ED7 0x61034584
0x61077A1F 0x61007A61 0x61007C47 0x
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The hanging problem that
I mentioned previously seems to be gone, too... or, more likely, it
will manifest itself 10 seconds
On Mon, Oct 21, 2002 at 10:42:45PM -0500, Gary R. Van Sickle wrote:
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The hanging problem
that I mentioned previously seems to be gone,
On Mon, Oct 21, 2002 at 10:42:45PM -0500, Gary R. Van Sickle wrote:
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The hanging problem
that I mentioned previously seems to be
I was able to duplicate Jason's mmap problem with his version of exim
and, so, I think I was also able to fix it.
The latest snapshot should solve this problem. The hanging problem that
I mentioned previously seems to be gone, too... or, more likely, it
will manifest itself 10 seconds after I
Jason Tishler wrote
$ tail -1 /var/spool/exim/log/mainlog
2002-10-18 16:18:23 daemon: fork of queue-runner process failed: Resource
temporarily unavailable
$ ps -ef
exim 6481096 ? 16:18:22 /usr/local/bin/exim-4.10-1
That's probably a privately compiled exim.
Does it use special
Just another datapoint. On XP SP1 + Cygwin 1.3.13-2, here's what I get
whenever something tries to fork:
O:\c:\cygwin\bin\bash
bash-2.05b$ ls
8 [main] bash 3952 fixup_mmaps_after_fork: base address fails to match req
uested address 0xBD
c:\cygwin\bin\bash.exe: ***
On Thu, Oct 17, 2002 at 02:12:18PM -0400, Rob Napier wrote:
Just another datapoint. On XP SP1 + Cygwin 1.3.13-2, here's what I get
whenever something tries to fork:
O:\c:\cygwin\bin\bash
bash-2.05b$ ls
8 [main] bash 3952 fixup_mmaps_after_fork: base address fails to match req
uested address
serious! Anyone know of a good course on humor?
;-)
Larry
Original Message:
-
From: Christopher Faylor [EMAIL PROTECTED]
Date: Thu, 17 Oct 2002 14:29:52 -0400
To: [EMAIL PROTECTED]
Subject: Re: latest cvs fork problems
On Thu, Oct 17, 2002 at 02:12:18PM -0400, Rob Napier wrote:
Just
On Mon, Oct 14, 2002 at 11:14:46AM -0400, Christopher Faylor wrote:
On Sun, Oct 13, 2002 at 10:32:23PM -0500, Steve O wrote:
On Mon, Oct 14, 2002 at 03:09:50AM -, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:
Sorry, only subscribers may post. See the project web page for details:
Chris,
On Thu, Oct 17, 2002 at 02:29:52PM -0400, Christopher Faylor wrote:
On Thu, Oct 17, 2002 at 02:12:18PM -0400, Rob Napier wrote:
Just another datapoint. On XP SP1 + Cygwin 1.3.13-2, here's what I get
whenever something tries to fork:
O:\c:\cygwin\bin\bash
bash-2.05b$ ls
8
On Fri, Oct 18, 2002 at 08:23:21AM -0400, Jason Tishler wrote:
Chris,
On Thu, Oct 17, 2002 at 02:29:52PM -0400, Christopher Faylor wrote:
On Thu, Oct 17, 2002 at 02:12:18PM -0400, Rob Napier wrote:
Just another datapoint. On XP SP1 + Cygwin 1.3.13-2, here's what I get
whenever something tries
Chris,
On Fri, Oct 18, 2002 at 10:23:40AM -0400, Christopher Faylor wrote:
Can you send cygcheck output as an attachment?
See attached.
Jason
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Fri Oct 18 11:05:16 2002
Windows 2000 Professional Ver 5.0 Build 2195 Service Pack
Chris,
On Fri, Oct 18, 2002 at 10:23:40AM -0400, Christopher Faylor wrote:
I still can't duplicate this.
A binary search of the recent snapshots indicates that 2002-Oct-14 is OK
but 2002-Oct-15 is not. So, I think that we can conclude that one of
the following changes is the culprit:
On Fri, Oct 18, 2002 at 11:13:19AM -0400, Jason Tishler wrote:
Chris,
On Fri, Oct 18, 2002 at 10:23:40AM -0400, Christopher Faylor wrote:
Can you send cygcheck output as an attachment?
See attached.
Are you running something like cygserver that would be using shared memory?
I don't see why
Chris,
On Fri, Oct 18, 2002 at 03:34:39PM -0400, Christopher Faylor wrote:
Are you running something like cygserver that would be using shared
memory?
No.
I don't see why shared memory would be a problem running bash.
$ uname -a
CYGWIN_NT-5.0 TISHLERJASON 1.3.14s(0.62/3/2) 20021015 13:13:49
On Fri, Oct 18, 2002 at 04:27:46PM -0400, Jason Tishler wrote:
On Fri, Oct 18, 2002 at 03:34:39PM -0400, Christopher Faylor wrote:
Are you running something like cygserver that would be using shared
memory?
No.
Ok. Do you have an exim config file, then? I don't see it doing anything
with
On Fri, Oct 18, 2002 at 08:09:44PM -0400, Christopher Faylor wrote:
On Fri, Oct 18, 2002 at 04:27:46PM -0400, Jason Tishler wrote:
On Fri, Oct 18, 2002 at 03:34:39PM -0400, Christopher Faylor wrote:
Are you running something like cygserver that would be using shared
memory?
No.
Ok. Do you have
Same here with 1.3.13-2; it seems that all programs are affected (e.g. I can't run
anything from bash since bash can't fork). I'm using WIndows XP SP1.
Steve O [EMAIL PROTECTED] writes:
On Mon, Oct 14, 2002 at 03:09:50AM -, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:
Sorry, only
On Sun, Oct 13, 2002 at 10:32:23PM -0500, Steve O wrote:
On Mon, Oct 14, 2002 at 03:09:50AM -, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:
Sorry, only subscribers may post. See the project web page for details:
http://www.cygwin.com/lists.html (#5.7.2)
Hi,
I was trying to get the latest
On Mon, Oct 14, 2002 at 02:28:42PM +0400, Roman Belenov wrote:
Same here with 1.3.13-2; it seems that all programs are affected (e.g.
I can't run anything from bash since bash can't fork). I'm using
WIndows XP SP1.
cygcheck output would confirm if this is really 1.3.13-2 that you're running.
On Mon, Oct 14, 2002 at 03:09:50AM -, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:
Sorry, only subscribers may post. See the project web page for details:
http://www.cygwin.com/lists.html (#5.7.2)
Hi,
I was trying to get the latest cygwin CVS working and ran into some
difficulties. An
28 matches
Mail list logo
