Bug 168812 - EMBOSS execution issue with gcc-3.2.3-52.x86_64
Summary: EMBOSS execution issue with gcc-3.2.3-52.x86_64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gcc
Version: 3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-20 14:53 UTC by Tru Huynh
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-20 19:25:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tru Huynh 2005-09-20 14:53:57 UTC
Description of problem:
gcc-3.2.3-52.x86_64 can't compile a proper EMBOSS-3.0.0 version
stock gcc-3.4.3 is ok

Version-Release number of selected component (if applicable):
gcc-3.2.3-52.x86_64

How reproducible:
always

Steps to Reproduce:
1.wget ftp://ftp.uk.embnet.org/pub/EMBOSS/EMBOSS-3.0.0.tar.gz
2. tar xzvf EMBOSS-3.0.0.tar.gz
3. cd EMBOSS-3.0.0 ; ./configure; make
4. ./emboss/embossversion
  
Actual results:
[tru@bobo EMBOSS-3.0.0]$ ./emboss/embossversion
Segmentation fault (core dumped)

Expected results:
[tru@sillage EMBOSS-3.0.0]$ ./emboss/embossversion 
Writes the current EMBOSS version number
3.0.0


Additional info:

Comment 1 Jakub Jelinek 2005-09-20 19:25:46 UTC
That can very likely be application bug, the fact that it passes with one
compiler and doesn't with another one doesn't say anything, the program can
still be in undefined code territory.
For a bug to be filed here, you need to debug it yourself and only if you prove
it is compiler bug, you need to create a (small) self-contained testcase and
attach it here.

Alternatively, if you have Red Hat support contract, you can deal with it that
way.

Comment 2 Tru Huynh 2005-09-22 13:35:13 UTC
For what it's worth, the same behaviour is observed on 3.6beta version
gcc-3.2.3-53.x86_64/glibc-devel-2.3.2-95.35.x86_64.

I will try to come up with a shorter testcase.


Note You need to log in before you can comment on or make changes to this bug.