public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: httpd immediate segfault on startup
Date: Mon, 03 Aug 2015 06:46:00 -0000	[thread overview]
Message-ID: <55BF0E48.7010207@jhmg.net> (raw)
In-Reply-To: <55BE58E6.2040801@gmail.com>

On 8/2/2015 10:52 AM, Marco Atzeri wrote:
> On 7/31/2015 6:18 PM, Jim Garrison wrote:
>> On 7/26/2015 5:24 PM, Jim Garrison wrote:
>>> Updated all cygwin packages to current versions, installed httpd
>>> 2.4.16-1.  On startup httpd segfaults:
>>>
>>> Exception: STATUS_ACCESS_VIOLATION at eip=65DC5D78
>>> eax=8004E028 ebx=00000001 ecx=00000000 edx=8004DFF0 esi=80014490
>>> edi=80016498
>>> ebp=0028CC78 esp=0028CB5C program=C:\cygwin\usr\sbin\httpd.exe, pid
>>> 25500, thread main
>>> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>>> Stack trace:
>>> Frame     Function  Args
>>> 0028CC78  65DC5D78 (00000003, 0028CC9C, 80010100, 00000020)
>>> 0028CD28  6100846A (00000000, 0028CD84, 610074F0, 00000000)
>>> End of stack trace
>>
>> Is the maintainer of the httpd package on the list? If not, can
>> someone provide a point of contact? I'd like to investigate this if
>> possible but need guidance on how to proceed.
>>
> 
> He is on the list, but a bit busy I would say.
> 
> the second frame address is
> 
>  $ addr2line.exe -e /usr/bin/cygwin1.dll 0x6100846A
> /usr/src/debug/cygwin-2.1.0-1/winsup/cygwin/dcrt0.cc:1041
> 
>       cygwin_exit (user_data->main (__argc, newargv, *user_data->envptr));
> 
> so it seems that the process initialization went wrong.
> Have you tried to reinstall httpd ?
> May be the file was damaged
> It should be
> 
> 2015-07-19 19:43      754717 usr/sbin/httpd.exe
> 
> The first address 65DC5D78 seems over the cygwin area.
> 
> Cheers
> Marco

I tried reinstalling with no luck.

I think the exception and stack trace are secondary to the main
problem, which is described by the two messages in the error_log:

(88)Function not implemented: AH00023: Couldn't create the proxy mutex
(88)Function not implemented: AH02478: failed to create proxy mutex

The exception goes away if I remove mod_perl from the configuration,
but the errors and failure to configure are the same.  I also tried
launching httpd in a mintty shell that was started with administrator
privilege level, but the same error occurs.

The "Function not implemented" seems to indicate something mis-matched
in my system but I cannot figure out what.

-- 
Jim Garrison (jhg@acm.org)
PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88

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

  reply	other threads:[~2015-08-03  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27  0:24 Jim Garrison
2015-07-29 15:48 ` Jim Garrison
2015-07-29 16:21   ` Habermann, David (D)
2015-07-31 16:18 ` Jim Garrison
2015-08-02 17:52   ` Marco Atzeri
2015-08-03  6:46     ` Jim Garrison [this message]
2015-08-25 15:48       ` httpd immediate segfault on startup [solution] Jim Garrison
2015-11-18  8:56         ` nemozny

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=55BF0E48.7010207@jhmg.net \
    --to=jhg@jhmg.net \
    --cc=cygwin@cygwin.com \
    --cc=jhg@acm.org \
    /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).