os-solaris/5013: > Segmentation Fault - core dumped during compilation

[St...@hyperreal.org, "F." <fr...@rivo.dlo.nl>]

>Number:         5013
>Category:       os-solaris
>Synopsis:       > Segmentation Fault - core dumped during compilation
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Sep 15 06:10:01 PDT 1999
>Last-Modified:
>Originator:     franks@rivo.dlo.nl
>Organization:
apache
>Release:        1.3.9
>Environment:
> SunOS orca 5.7 Generic_106541-02 sun4u sparc SUNW,Ultra-4
> gcc version 2.95.1 19990816 (release)
>Description:
I compiled the new release 1.3.9 on Solaris 2.7 using SUN's cc compiler. That went seamless. It is up and running. But before that i tried to use our (new) default gcc compiler (GCC 2.95.1). This gave some core dumps. I'am not sure where to put this problem, at your organization or at gcc-bugs@gcc.gnu.org.

A llisting of the terminal in and output follows.

regards

---
orca# gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/specs
gcc version 2.95.1 19990816 (release)
orca# uname -a
SunOS orca 5.7 Generic_106541-02 sun4u sparc SUNW,Ultra-4
orca# ./configure
Configuring for Apache, Version 1.3.9
 + Warning: Configuring Apache with default settings.
 + This is probably not what you really want.
 + Please read the README.configure and INSTALL files
 + first or at least run './configure --help' for
 + a compact summary of available options.
 + using installation path layout: Apache (config.layout)
Creating Makefile
Creating Configuration.apaci in src
Creating Makefile in src
 + configured for Solaris 270 platform
 + setting C compiler to gcc
 + setting C pre-processor to gcc -E
 + checking for system header files
 + adding selected modules
Segmentation Fault - core dumped
Segmentation Fault - core dumped
Segmentation Fault - core dumped
Segmentation Fault - core dumped
Segmentation Fault - core dumped
 + checking sizeof various data types
 + doing sanity check on compiler and options
Creating Makefile in src/support
Creating Makefile in src/os/unix
Creating Makefile in src/ap
Creating Makefile in src/main
Creating Makefile in src/lib/expat-lite
Creating Makefile in src/modules/standard
orca# setenv CC cc
orca# ./configure
Configuring for Apache, Version 1.3.9
 + Warning: Configuring Apache with default settings.
 + This is probably not what you really want.
 + Please read the README.configure and INSTALL files
 + first or at least run './configure --help' for
 + a compact summary of available options.
 + using installation path layout: Apache (config.layout)
Creating Makefile
Creating Configuration.apaci in src
Creating Makefile in src
 + configured for Solaris 270 platform
 + setting C pre-processor to cc -E
 + checking for system header files
 + adding selected modules
 + checking sizeof various data types
 + doing sanity check on compiler and options
Creating Makefile in src/support
Creating Makefile in src/os/unix
Creating Makefile in src/ap
Creating Makefile in src/main
Creating Makefile in src/lib/expat-lite
Creating Makefile in src/modules/standard
orca#

B
>How-To-Repeat:
download apache_1.3.9 and GCC_2.95.1 <ftp://nce/sun.ca/freeware/sparc/7/gcc-2.95.1-sol7-sparc-local.gz> on a Solaris 7 platform and see what happens...
>Fix:
I think gcc is doing it wrong... You will be ready quite fast.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]