Re: deadlock writing to stdout in remotely controlled soffice

On 12/04/2013 07:13 AM, Markus Mohrhard wrote:
> Thread 2 (Thread 0x7fb868e6f700 (LWP 22391)):
> #0  0x000000352d4e767d in write () from /lib64/libc.so.6
> #1  0x000000352d476d53 in _IO_new_file_write () from /lib64/libc.so.6
> #2  0x000000352d4774ef in __GI__IO_file_xsputn () from /lib64/libc.so.6
> #3  0x000000352d46c73d in fputs () from /lib64/libc.so.6
> #4  0x00007fb88e855cb3 in (anonymous namespace)::log (level=SAL_DETAIL_LOG_LEVEL_WARN, area=0x7fb8748331b9 
> "legacy.osl",
>     where=0x7fb874833358 "/home/buildslave/source/libo-core/sc/source/core/data/documen7.cxx:276: ", 
> message=0x7fb868e6bbf0 "RemoveFromFormulaTree: nFormulaCodeInTree < nRPN")
>     at /home/buildslave/source/libo-core/sal/osl/all/log.cxx:242
> #5  0x00007fb88e855ee3 in osl::detail::logFormat (level=SAL_DETAIL_LOG_LEVEL_WARN, area=0x7fb8748331b9 
> "legacy.osl",
>     where=0x7fb874833358 "/home/buildslave/source/libo-core/sc/source/core/data/documen7.cxx:276: ", 
> format=0x7fb87483316b "%s", arguments=0x7fb868e6c038)
>     at /home/buildslave/source/libo-core/sal/osl/all/log.cxx:282
> #6  0x00007fb88e855e2b in sal_detail_logFormat (level=SAL_DETAIL_LOG_LEVEL_WARN, area=0x7fb8748331b9 
> "legacy.osl",
>     where=0x7fb874833358 "/home/buildslave/source/libo-core/sc/source/core/data/documen7.cxx:276: ", 
> format=0x7fb87483316b "%s") at /home/buildslave/source/libo-core/sal/osl/all/log.cxx:265

I assume stderr is a pipe nobody's reading from in a timely way, so that 
writing to it eventually blocks.

Stephan