X-Spam-Check-By: sourceware.org
Date: Thu, 17 Aug 2006 16:09:42 -0500
From: Brian Ford <Brian DOT Ford AT FlightSafety DOT com>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Snapshot uploaded, please try
In-Reply-To: <20060810212525.GA11554@trixie.casa.cgf.cx>
Message-ID: <Pine.CYG.4.58.0608171608550.2408@PC1163-8460-XP.flightsafety.com>
References: <20060810142651 DOT GA32470 AT trixie DOT casa DOT cgf DOT cx>  <82k65gp9v0 DOT fsf AT vzell-de DOT de DOT oracle DOT com> <20060810212525 DOT GA11554 AT trixie DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, 10 Aug 2006, Christopher Faylor wrote:

> On Thu, Aug 10, 2006 at 11:19:15PM +0200, Dr. Volker Zell wrote:
> >>>>>> Christopher Faylor writes:
> >
> >    > The latest snapshot has been uploaded.
> >    > If you have been asked to test a snapshot, please try this one.  It contains
> >    > additional debugging which may help track down the "Xemacs problem".
> >
> >    > The error messages will be going to stderr, so if possible redirect the
> >    > output to a file for capture.
> >
> >
> >I haven't got Xemacs or rxvt in the defunct state yet, but starting rxvt
> >or ps/procps/pstree gives:
> >
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
>
> Those are true errors but they should not be responsible for your problems.
>
> >Starting xterm from an rxvt window gives:
> >
> >In the Rxvt window
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >CloseHandle(*h) failed _onreturn::~_onreturn():1102
> >
> >In the Xterm window
> > 587214 [main] xterm 296 modify_handle: virtual void fhandler_pipe::set_close_on_exec(bool):175 handle guard<0x680> not found
>
> That one *could* be responsible.  I was suspecting something in the pipe
> code since it has often been the cause of handle closing confusion.
>
> >Will follow up, when one of the process go to defunct state.
>
> I think I could pinpoint this pretty quickly if I could think of some
> way to have cygwin dump the list of handles that it knows about and
> their states.  Maybe I could get strace to do that when you first attach
> to a running cygwin process.  I'll have to think about that but I guess
> that means that there is another snapshot coming.
>
> I know that Corinna has some experimental code coming which is intended
> to work around the apparent Windows CreateFileMapping bug.
>
> cgf
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>

-- 
Brian Ford
Lead Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained crew...

.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/