public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sergey Okhapkin <sos@prospect.com.ru>
To: GNU Win 32 <gnu-win32@cygnus.com>,
	"'Colman Curtin'" <ccurtin@trintech.com>
Subject: RE: forking vim gui
Date: Fri, 10 Oct 1997 23:40:00 -0000	[thread overview]
Message-ID: <01BCD632.343FDA40@sos> (raw)

Colman Curtin wrote:
> folks
> Having successfully compiled my fav editor vim a while back.
> How come when I launch it as 'gvim' or 'vim -g' which causes vim to fork 
the
> gui version I get an exception.
> However if I launch it as 'vim -g -f' which launches the gui but doesn't
> return to the shell it work fine.
> But if I launch it as above but use bash to background it 'vim -g -f &' 
it all
> works fine and I get bash back?
>
> vim5.0m, Sergey's latest dll and bash, win95 16MB
>
> any ideas?

It's a bug of cygwin - .bss/.data sections of dll's are not copied to a 
child on fork(). Someone in this list wrote about related fixes he made, 
but I never saw the fixes itself :-(

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-10-10 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-10 23:40 Sergey Okhapkin [this message]
1997-10-12 22:05 ` Victor Hugo Ochoa Garza
1997-10-13  9:19   ` Jesse L. Marlin
1997-10-13 10:28   ` Bartlee A. Anderson
1997-10-13 19:00   ` Charles Curley
  -- strict thread matches above, loose matches on Subject: below --
1997-10-10  3:18 Colman Curtin
1997-10-11 12:53 ` Alex

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=01BCD632.343FDA40@sos \
    --to=sos@prospect.com.ru \
    --cc=ccurtin@trintech.com \
    --cc=gnu-win32@cygnus.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).