Bug 470993
Summary: | GCC 4.1.2 crashes when compiling ImageMagick 6.4.5.5 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jari Turkia <redhat-bugzilla> | ||||
Component: | gcc | Assignee: | Jakub Jelinek <jakub> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | BaseOS QE <qe-baseos-auto> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.2 | CC: | law | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-11-26 19:52:31 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: | |||||||
Attachments: |
|
Description
Jari Turkia
2008-11-11 09:59:42 UTC
Created attachment 323165 [details]
GCC crash dump
This is the crash dump file which GCC instructed to include in the bug report.
We could need additional information to diagnose this problem. I downloaded ImageMagik 6.4.5.5 onto a RHEL 5.2, configured it per your instructions and it built just fine. I also worked with the attachment .i file and passed it through the compiler with various options to try and trip the failure without success. To proceed further you'd need to reproduce the failure. Then provide the proper .i file and command line that was passed to GCC to trigger the failure. Jari Turkia 2008-11-11 05:00:59 EST Jeff Law 2013-11-26 14:52:31 EST <sarcasm> What?! Insufficient data? During last 5 years you failed to find enough data in my bug report. </sarcasm> Never mind. RHEL 6 was released about 2 years after filing this bug report and for the last 3 years, I've been using that. Btw. ImageMagick compiles ok with GCC 4.4.7. Someone should have asked for the additional information when the report was originally filed, but sadly that didn't happen and AFAICT, this bug fell through the cracks repeatedly. We're currently reviewing every remaining open toolchain bug reported against RHEL 5, thus it was on my radar after all this time. I would have liked to have been able to trigger the failure so I could dive in a bit further and say conclusively that it was fixed and get a regression test added to GCC's regression suite. But my attempts to trigger the failure were not successful. |