public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jason Tishler <jason@tishler.net>
To: cygwin@cygwin.com
Subject: Re: Apache 1.3.22 on cygwin under XP - loosing data
Date: Wed, 29 May 2002 10:16:00 -0000	[thread overview]
Message-ID: <20020529142423.GA2660@tishler.net> (raw)
In-Reply-To: <3CF4CA4C.8EE1E771@insight.rr.com>

Paul,

On Wed, May 29, 2002 at 08:32:13AM -0400, Paul McFerrin wrote:
> I had to rebase everything manually myself.  Without the rebase, the
> httpd processes could not even complete a fork!

The above is a well known issue that affects other Cygwin applications
such as Python too.

> The arguments that I used were the same used by someone else for a
> different application and not specificially Apache.

The above is correct.

> I've asked someone to shed some light on educating me on just what
> those arguments mean so I don't have to be in the dark on this subject.

The options to my rebase tool:

    $ rebase     
    usage: rebase -b BaseAddress [-d] [-o Offset] ImageFileName ...

have the same semantics as the ones supported by MS's tool:

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/perfutil_2z39.asp

I added the "-o Offset" option to spread out the base address by an
extra Offset amount because packing the DLLs "too close" can Cygwin's
fork() to still fail.

> Heck I really don't know if they are suitable for Apache.

Rebasing is suitable for all Cygwin apps that suffer from the DLL base
address conflict fork() issue.  Unfortunately, some DLLs do not survive
the rebase process.  It is yet to be determined why.  Want to help
figure this out?

> I too would like to get this issue resolved.

Me too.  The rebase functionality will ultimately be integrated into
Cygwin's setup.exe.

> Jason are you listening?

Yes.  Hmm...

Jason

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2002-05-29 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000501c20556$c66b43c0$bd7ba8c0@q6f3d6>
2002-05-28  2:32 ` Paul McFerrin
2002-05-28  4:01   ` djnews
     [not found]     ` <3CF2FD22.D8A5D3B9@insight.rr.com>
     [not found]       ` <000701c206dc$f66a7960$bd7ba8c0@q6f3d6>
2002-05-29  8:46         ` Paul McFerrin
2002-05-29 10:16           ` Jason Tishler [this message]

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=20020529142423.GA2660@tishler.net \
    --to=jason@tishler.net \
    --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).