Bug Hunting Session
Bug 58043 - truncated files left over?
Summary: truncated files left over?
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-12-09 12:59 UTC by Lionel Elie Mamane
Modified: 2018-08-17 02:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Lionel Elie Mamane 2012-12-09 12:59:45 UTC
In my libreoffice-3-6 tree, after a "make" aborted because not enough space on hard disk, a subsequent "make" (after freeing enough space on the disk) fails with errors such as:

terminate called after throwing an instance of 'CppUnit::DynamicLibraryManagerException'
  what():  Failed to load dynamic library: /home/master/src/libreoffice/workdirs/libreoffice-3.6/workdir/unxlngx6/LinkTarget/CppunitTest/libtest_filter_tiff_test.so

terminate called after throwing an instance of 'CppUnit::DynamicLibraryManagerException'
  what():  Failed to load dynamic library: /home/master/src/libreoffice/workdirs/libreoffice-3.6/workdir/unxlngx6/LinkTarget/CppunitTest/libtest_filter_tga_test.so

terminate called after throwing an instance of 'CppUnit::DynamicLibraryManagerException'
  what():  Failed to load dynamic library: /home/master/src/libreoffice/workdirs/libreoffice-3.6/workdir/unxlngx6/LinkTarget/CppunitTest/libtest_hwpfilter_test_hwpfilter.so

My presumption is that these files (or a .o file contained in them) were created, but left truncated after the "ENOSPC" error. When the build ofa file fails after it has been partially written to disk, it should be deleted, else make will never try to remake it.

Ideally the compiler / linker / ... should do that, but if it does not, we can wrap each call to a compiler / linker / ... in something like

 set -e; $(CC) "$<" || ( RET=$?; rm -f "$<"; exit $? )
Comment 1 Joel Madero 2013-07-02 05:41:15 UTC
@Lionel - marking as NEW as it's you, if this problem does not persist or you want independent confirmation please let us know and someone from QA will attempt to reproduce
Comment 2 QA Administrators 2015-04-01 14:41:44 UTC Comment hidden (obsolete)
Comment 3 tommy27 2016-04-16 07:28:01 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2017-05-22 13:25:33 UTC Comment hidden (obsolete)
Comment 5 Jean-Baptiste Faure 2017-08-15 17:07:29 UTC
Hi Lionel,

Does "make distclean" fix the problem?

Best regards. JBF
Comment 6 Lionel Elie Mamane 2017-08-16 08:05:55 UTC
(In reply to Lionel Elie Mamane from comment #0)
>  set -e; $(CC) "$<" || ( RET=$?; rm -f "$<"; exit $? )

That should be:

set -e; $(CC) "$<" || ( RET=$?; rm -f "$<"; exit $RET )

(In reply to Jean-Baptiste Faure from comment #5)
> Does "make distclean" fix the problem?

Four and a half years later, I don't have a copy of the corrupted build tree to test. However, since the problem is truncated output files, my prediction is that yes, even "make clean" is enough.

I still stand on my solution, as corrected above.
Comment 7 QA Administrators 2018-08-17 02:37:57 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team