Bug 11493 - ld gives no error message when disk space is exhausted
Summary: ld gives no error message when disk space is exhausted
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: binutils
Version: 1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-05-17 22:34 UTC by Havoc Pennington
Modified: 2007-11-30 22:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-28 16:35:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Havoc Pennington 2000-05-17 22:34:34 UTC
If disk space is exhausted during linking, ld exits with a failure
code but doesn't print strerror() from the failed disk write,
leaving users wondering what went wrong.

Comment 1 Miloslav Trmac 2004-02-05 07:43:42 UTC
This still happens in FC 1 (binutils-2.14.90.0.6-4).

Comment 2 Matthew Miller 2006-07-11 17:48:58 UTC
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.

Thanks!

NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.



Comment 3 John Thacker 2006-10-28 16:35:18 UTC
Closing per lack of response to previous comment.  Note that FC1 and FC2 are no
longer supported even by Fedora Legacy.  If this still occurs on FC3 or FC4,
please assign to that version and Fedora Legacy.  If it still occurs on FC5 or
FC6, please reopen and assign to the correct version.


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