public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin@cygwin.com
Subject: Re: MapViewOfFileEx errors with cygwin1-20040716 snapshot
Date: Wed, 21 Jul 2004 01:15:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.58.0407202057250.10093@slinky.cs.nyu.edu> (raw)
In-Reply-To: <20040720151642.GL11473@cygbert.vinschen.de>

On Tue, 20 Jul 2004, Corinna Vinschen wrote:

> On Jul 20 15:53, Dr. Volker Zell wrote:
> > Well my MapViewOfFileEx errors are still there, but that seems to be a
> > different problem.
>
> I tried to reproduce that problem with my shm test application which
> forks twice, but to no avail.
>
> A simple testcase(tm) would be helpful.
>
> Corinna

Corinna,

FWIW, I just saw this error for the first time with the above snapshot
(Win2k SP3).  The command that triggered it was a "cvs diff" run from vim
(":!cvs diff"), if it makes any difference.  No idea what caused it, since
all of the subsequent invocations of the exact same command (from the same
vim session) succeeded.  I've been unable to reproduce it since, so this
is just a quick confirmation that it's not only Volker's environment.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/

  reply	other threads:[~2004-07-21  1:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 14:09 MapViewOfFileEx errors disappeared " Dr. Volker Zell
2004-07-19  5:14 ` Christopher Faylor
2004-07-19 11:47   ` Dr. Volker Zell
2004-07-19 18:01     ` Christopher Faylor
2004-07-20 12:11     ` Corinna Vinschen
2004-07-20 13:56       ` Dr. Volker Zell
2004-07-20 16:26         ` Corinna Vinschen
2004-07-21  1:15           ` Igor Pechtchanski [this message]
2004-07-21 10:14             ` MapViewOfFileEx errors " Corinna Vinschen
2004-07-21 18:57               ` Igor Pechtchanski
2004-07-21 20:53                 ` Corinna Vinschen
2004-07-21 22:46                   ` Igor Pechtchanski
2004-07-22 17:03                     ` Igor Pechtchanski
2004-07-22 17:20                       ` Igor Pechtchanski
2004-07-22 17:53                         ` Dave Korn
2004-07-22 17:47                       ` Dave Korn
2004-07-22 20:58                         ` Corinna Vinschen
2004-07-23 12:38                           ` Dave Korn
2004-07-22 19:17                       ` Christopher Faylor
2004-07-25 12:19                         ` Christopher Faylor
2004-07-26  7:48                           ` Igor Pechtchanski
2004-07-26  7:54                             ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.58.0407202057250.10093@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).