Summary: | app-office/libreoffice-3.5.6.2 - In member function 'virtual void SdXML3DPolygonBasedShapeContext::StartElement(const com::sun::...)': .../work/libreoffice-core-3.5.6.2/xmloff/source/draw/ximp3dobject.cxx:454:1: internal compiler error: Segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stephan Hartmann (RETIRED) <sultan> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
Stephan Hartmann (RETIRED)
2012-09-14 12:55:07 UTC
Created attachment 323754 [details]
build log
[ build CXX ] xmloff/source/draw/ximplink /var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/xmloff/source/draw/ximp3dobject.cxx: In member function 'virtual void SdXML3DPolygonBasedShapeContext::StartElement(const com::sun::star::uno::Reference<com::sun::star::xml::sax::XAttributeList>&)': /var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/xmloff/source/draw/ximp3dobject.cxx:454:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.gentoo.org/> for instructions. make[2]: *** [/var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/workdir/unxlngx6.pro/CxxObject/xmloff/source/draw/ximp3dobject.o] Error 1 make[2]: *** Waiting for unfinished jobs.... [ build CXX ] vcl/source/gdi/pdfextoutdevdata Could you please provide some plausible information to rule out that you didn't merely run out of RAM? Like, try with fewer make jobs and remove -pipe from your CXXFLAGS. Machine has 8GB physical RAM and 16GB swap. 10GB of disk space are available for building. Removed '-pipe' from CFLAGS/CXXFLAGS and set MAKEOPTS="-j1". Now it compiles successfully. However, '-pipe' is added in most Makefiles anyway. During compile I observed that there are sometimes two 'cc1plus' process running. Maybe the check for available RAM should be adjusted (200MiB)? (In reply to comment #4) > Machine has 8GB physical RAM and 16GB swap. 10GB of disk space are available > for building. 9 jobs times a gigabytes or more each would easily consume all RAM, and swap doesn't help in this case as GCC won't use it. Unfortunately, GCC doesn't handle running out of memory very well so you get a segmentation fault where it really ought to just try again. > Maybe the check for available RAM should be adjusted (200MiB)? It says "512M" now, which would generally work if you disabled profiling and -pipe, and used a single make job. Assigning, then. Just found out that one of the memory modules had a defect. After replacing the module everything compiles fine even with MAKEOPTS="-j9". |