Bug 19545 - gcc segfaults when compiling wv-0.6.1
Summary: gcc segfaults when compiling wv-0.6.1
Keywords:
Status: CLOSED DUPLICATE of bug 19392
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gcc
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-22 13:29 UTC by Nick Urbanik
Modified: 2007-04-18 16:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-10-22 13:38:40 UTC
Embargoed:

Attachments (Terms of Use)
The spec file I used with rpm -ba wv.spec (2.30 KB, text/plain)
2000-10-22 13:32 UTC, Nick Urbanik 		no flags Details
The output of rpm -ba wv.spec 2>&1 | tee wv.spec-2.log (42.56 KB, text/plain)
2000-10-22 13:35 UTC, Nick Urbanik 		no flags Details
View All

Description Nick Urbanik 2000-10-22 13:29:55 UTC 
I edited the wv.spec from 7.0 powertools to update to wv-0.6.1.
rpm -ba results in a segfault from gcc.
Attached: the spec file I used, and the output from the compilation.
Comment 1 Nick Urbanik 2000-10-22 13:32:27 UTC 
Created attachment 4493 [details]
The spec file I used with rpm -ba wv.spec
Comment 2 Nick Urbanik 2000-10-22 13:35:15 UTC 
Created attachment 4494 [details]
The output of rpm -ba wv.spec 2>&1 | tee wv.spec-2.log
Comment 3 Nick Urbanik 2000-10-22 13:38:38 UTC 
Note: this is an upgraded RH system, with all updates applied, including
glibc-2.1.94-3.i686.rpm.  This is a PIII.

I'm sorry I don't have time to produce a minimal program to reproduce this bug,
but perhaps you people may wish to follow this up.
Comment 4 Jakub Jelinek 2000-10-23 07:42:23 UTC 
The wv part should be fixed in wv 0.6.2 (at least wv developers told me),
the gcc segfault (gcc should obviously not crash even on bad input) is fixed
in 2.96-57 (in rawhide) and above and will appear in the next gcc errata.

*** This bug has been marked as a duplicate of 19392 ***
Note You need to log in before you can comment on or make changes to this bug.