httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44639] Segmentation fault 11 errors right after server started up
Date Thu, 20 Mar 2008 22:14:39 GMT

Dave <> changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |ASSIGNED

--- Comment #13 from Dave <>  2008-03-20 15:14:39 PST ---
(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #7)
> > > (In reply to comment #4)
> > > > (In reply to comment #2)

> > > 
> > > This issue occurred on a Customer production box that does not have debug tool
> > > like gdb.
> > > Also, the Apache we built is using Sun's cc compiler, not the g++. Doesn't
> > > only debug symbols that are generated by g++? The stack traces I provided above
> > > was from a core dump using Sun's workshop (dbx). I can email you the core 
> You cannot do this on your local box. This only works on the box that generated
> the core unless your box is a perfect clone of the box where the core dump
> happened :-).
> Nevertheless, googling around I found similar reports of crashes in Samba and
> other applications that all fail when using initgroups on Solaris 9, so this
> could be a Solaris 9 bug.
> I am no dbx expert, but it would be nice to know what string is stored at
> 0x4efbb0.
> Furthermore please provide the settings of the User and Group directives in
> your httpd.conf and the name of the group with the id 101.

Yes, my box is not quite the same although both are Solaris 9. Also mine uses
NIS rather than LDAP.

Here are the settings of User and Group in httpd.conf
User       ehealth
Group      ehealth

The group id 101 (x65) is ehealth, so that does match the one in httpd.conf.

As for Solaris 9, but why the Apache 1.3 works fine on the same server? That's
why I questioned that the os level of authentication is not transparent to

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message