Bug 163599
Summary: | /usr/bin/ld: BFD 2.15.92.0.2 20040927 internal error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Chester Hosey <chester.hosey> |
Component: | binutils | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-21 18:50:52 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
Chester Hosey
2005-07-19 13:00:42 UTC
This can happen if some other process removes or truncates one or more of the input files (.o objects resp. .a libraries) given to the linker on the command line between the initial linking phase and the end of the link. As such, it would be a dependency bug in the makefiles of the project you are compiling. So how about a helpful error message? You're telling me that the bug (or NOTABUG, despite ld telling me that there was an internal error) is caused by the input. How about an error message that doesn't explicitly tell me to file a bug report? Do you honestly believe that this error message is optimal and provides the user with the information they need in order to respond to the problem? If not, isn't that considered a bug somehow? The linker relies in many places that the input files are not changed during linking and can result in all sorts of crashes. The linker does not load everything into memory, because that would preclude linking really large binaries or shared libraries. Yes, it can be considered a bug, but it is certainly not the only one if you change the input files while linking, so IMHO not worth doing changing. |