On 12/20/2016 09:29 AM, Stephan Bergmann wrote:
idlc spawns a child process exec'ing ucpp; this backtrace is apparently
from that child process, doing

            SAL_INFO("sal.osl", "ChildStatusProc : starting " <<
data.m_pszArgs[0]);

(sal/osl/unx/process.cxx:208) before calling execv.  Why that
std::ostringstream operator << would go into an endless loop allocating
(ever more?) memory (if that is what that "Analysis of sampling idlc"
claims), I have no idea.  Would need further debugging.

ach, <https://cgit.freedesktop.org/libreoffice/core/commit/?id=ffadee038f5887f3ca427740140ddbfb4457e660> "Don't malloc between for and exec"
_______________________________________________
LibreOffice mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Reply via email to