Re: other/6903: gcc could give better error message when /tmp gets full

Re: other/6903: gcc could give better error message when /tmp gets full

[neroden]

Synopsis: gcc could give better error message when /tmp gets full

State-Changed-From-To: feedback->closed
State-Changed-By: neroden
State-Changed-When: Wed Mar 12 18:49:26 2003
State-Changed-Why:
    OS bug, not GCC bug, sadly.  Closing.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6903

Re: other/6903: gcc could give better error message when /tmp gets full

[ehrhardt]

Synopsis: gcc could give better error message when /tmp gets full

State-Changed-From-To: open->feedback
State-Changed-By: cae
State-Changed-When: Mon Dec  9 14:14:21 2002
State-Changed-Why:
    As Zack pointed out there's not much that gcc can do about this.
    Any objections if I close this one?
    
        regards   Christian
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6903

Re: other/6903: gcc could give better error message when /tmp gets full

[Zack Weinberg]

The following reply was made to PR other/6903; it has been noted by GNATS.

From: Zack Weinberg <zack@codesourcery.com>
To: 25824@bugs.debian.org
Cc: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: Re: other/6903: gcc could give better error message when /tmp gets full
Date: Sat, 1 Jun 2002 15:59:04 -0700

 On Sun, Jun 02, 2002 at 12:34:20AM +0200, Matthias Klose wrote:
 > 
 > merry$ gcc -Wall -Werror -Wmissing-prototypes -g -O2 -I.  -DSTDC_HEADERS=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 Test.c -o Test
 > cc1: /tmp/ccb04872: I/O error
 > 
 > This happened repeatedly when /tmp filled up during compilation (Test.c is
 > over a megabyte long)...  A better error message might mention "device
 > full" or some such.
 
 GCC is at the mercy of the operating system here; if it chooses to set
 errno to EIO instead of ENOSPC on a disk-full condition, and therefore
 strerror() returns "I/O error" instead of "Out of space on device", we
 can't do much about that.  (Or anyway I can't think of anything.
 Suggestions are welcome.)
 
 zw

other/6903: gcc could give better error message when /tmp gets full

[Matthias Klose]

>Number:         6903
>Category:       other
>Synopsis:       gcc could give better error message when /tmp gets full
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 01 15:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Charles Briscoe-Smith <cpbs@debian.org>
>Release:        3.1 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
	
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  gcc-3.1        3.1-2          The GNU C compiler.
ii  binutils       2.12.90.0.7-1  The GNU assembler, linker and binary utiliti
ii  libc6          2.2.5-6        GNU C Library: Shared libraries and Timezone
host: i386-linux
configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1ds2/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=$\(prefix\)/share/man --infodir=$\(prefix\)/share/info --with-gxx-include-dir=$\(prefix\)/include/g++-v3-3.1 --enable-shared --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --enable-clocale=gnu --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc i386-linux
>Description:
[ Reported to the Debian BTS as report #25824.
  Please CC 25824@bugs.debian.org on replies.
  Log of report can be found at http://bugs.debian.org/25824 ]

merry$ gcc -Wall -Werror -Wmissing-prototypes -g -O2 -I.  -DSTDC_HEADERS=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 Test.c -o Test
cc1: /tmp/ccb04872: I/O error

This happened repeatedly when /tmp filled up during compilation (Test.c is
over a megabyte long)...  A better error message might mention "device
full" or some such.

	
>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: