Stop stripping [truncating]!

[Pap, Kristof]

Title: RE: Stop stripping [truncating]!





Hello


This can be a real error, but I've never experienced any similar,
neither with binutils (I don't use it too heavily however), neither
with the original strip on the system, with different machines. But
I have realized, that on some systems (for example SunOS 5.x),
if you have quotas, and you are near to the limit, the linker and the
compiler write the files only partially without any message, and
you will realize the error only when you want to start something,
and maybe the strip utility you try to use behaves similarily.
But this is just an idea...


Kristof Pap



-----Original Message-----
From:   Michael Capito [SMTP:mikec@tgf.tc.faa.gov]
Sent:   26. august 1999 16:20
To:     help-gcc@gnu.org
Subject:        Stop stripping [truncating]!


To all,


    I have a question that there may or may not be an answer for.  Thus
I will open it up to all for whatever assistance you can provide.  Any
help is appreciated...


    When linking together packages, sporatically I will get a
file-truncated error.  I have found that this corresponds with the file
being "stripped" upon compilation.  (Verifyable by using the utility
"file [filename.o]") This happens completely arbitrarily.  In 50
compiles, all of them can be good, or 40 of them can be bad.


So thus, the question is...


    Why would a file get arbitrarily stripped [truncated] during
compilation?


Thanks in advance for any help that anyone can provide...



MC


--
Michael Capito              Target Generation Facility
Project Engineer            F.A.A. Technical Center
                            Atlantic City Airport, NJ 08405