Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 2 Jun 2004 18:41:10 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: "Dr. Volker Zell" cc: cygwin AT cygwin DOT com Subject: Re: MapViewOfFileEx errors with cygwin-1.5.10-3 and gnome apps In-Reply-To: <87ekoxbovh.fsf@vzell-de.de.oracle.com> Message-ID: References: <87zn7mcgdx DOT fsf AT vzell-de DOT de DOT oracle DOT com> <87ekoxbovh DOT fsf AT vzell-de DOT de DOT oracle DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Thu, 3 Jun 2004, Dr. Volker Zell wrote: > >>>>> Igor Pechtchanski writes: > > > Wasn't 20040525 completely broken? You could review the diffs between > > the snapshots (on the snapshot page), but I suspect you'd have better luck > > checking where the handle for MapViewOfFileEx comes from (Win32 error 6 = > > "Handle is invalid"). > > Igor > > Well there are just the following changes by cgf between the working dll > from may 20 and the one from may 25.: > > * winbase.h: Semi-revert previous patch as it caused strange behavior. > Use syntax similar to that recommended in mingw-dvlpr. > > * winbase.h: Add proper attributions for memory operands throughout. > > I'm not sure if these changes are the cause of my problems. > > Any hint how to find out what this handle is ? > > Ciao > Volker Volker, In my (outdated!) cvs checkout of winsup/cygwin, the error message you got appears in shm.cc (fixup_shms_after_fork) and shared.cc (open_shared). The first thing to find out is which one of them produced your message (the output of strace should help). The strace output should also contain handle values, so you can try to trace it backwards from the error... BTW, before you spend a lot of effort on debugging, here's a WAG: do you use cygserver? If so, did you reboot and/or restart cygserver after you upgraded? The above looks like a shared memory error, and shared memory is part of cygserver functionality... I know you said that you don't have multiple Cygwin DLLs in your path, but if you renamed your old cygwin1.dll before replacing it with the snapshot one, it may be possible that you have multiple copies of cygwin1.dll *in memory*. Same goes for other services, FWIW. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/