Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 115282

Summary: segmentation fault with gcc gnat (ADA) on AMD64
Product: Red Hat Enterprise Linux 3 Reporter: Ryan Finnie <ryan>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 3.0CC: jmorris, shillman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:01:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ryan Finnie 2004-02-10 06:21:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
Gecko/20031007 Firebird/0.7

Description of problem:
When I try to compile any ADA program (in the simplest case, the
conftest program used in gcc itself) on RHEL3 AMD64, gcc produces a
segfault.

Version-Release number of selected component (if applicable):
gcc-gnat-3.2.3-24

How reproducible:
Always

Steps to Reproduce:
1. echo 'procedure conftest is begin null; end conftest;' > conftest.adb
2. gcc -v -c conftest.adb

Actual Results:  # gcc -c -v conftest.adb
Reading specs from /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--host=x86_64-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
 /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/gnat1 -quiet -dumpbase
conftest.adb conftest.adb -o /tmp/cc0j6DGy.s
+===========================GNAT BUG
DETECTED==============================+
| 3.2.3 20030502 (3.2.3-13) (x86_64-redhat-linux-gnu) GCC error:     
     |
| internal error: Segmentation fault                                 
     |
| Error detected at conftest.adb:1:29                                
     |
| Please submit a bug report, see http://gcc.gnu.org/bugs.html.      
     |
| Include the entire contents of this bug box in the report.         
     |
| Include the exact gcc or gnatmake command that you entered.        
     |
| Also include sources listed below in gnatchop format               
     |
| (concatenated together with no headers between files).             
     |
+==========================================================================+

Please include these source files with error report

%��
����!��#��

compilation abandoned


Expected Results:  # gcc -v -c conftest.adb
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
 /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/gnat1 -quiet -dumpbase
conftest.adb conftest.adb -o /tmp/ccYmFZ8M.s
 as -V -Qy -o conftest.o /tmp/ccYmFZ8M.s
GNU assembler version 2.14.90.0.4 (i386-redhat-linux) using BFD
version 2.14.90.0.4 20030523


Additional info:

This also occurs in the AMD64 beta of Fedora Core 1.  RHEL3 x86
compiles correctly.

Comment 1 Jakub Jelinek 2004-02-10 17:35:32 UTC
Make sure you boot with: noexec=off noexec32=off
If that helps, it is a known kernel problem.

Comment 2 Ryan Finnie 2004-02-14 05:32:59 UTC
Yes, that helped.  Thanks.

What bug # is the kernel problem documented under?  I can't seem to
find it...

Comment 3 Suzanne Hillman 2004-02-17 21:13:55 UTC
Looks to be bug #111264, which I am about to close this as duplicate
against.

*** This bug has been marked as a duplicate of 111264 ***

Comment 4 John Morris 2004-05-02 00:50:17 UTC
*** Bug 121670 has been marked as a duplicate of this bug. ***

Comment 5 Red Hat Bugzilla 2006-02-21 19:01:09 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.