Hi Pavel, > thank you for your explanation. I have recompiled some modules with profiling > turned on. I > need its output to easily see OO.o execution path. However my profiling logs > are empty :-( > They only contain data when OO.o is successfully started and terminated.
That's difficult to diagnose from remote :-\, but what you describe sounds to me as if you want to use OSL_TRACE, not RTL_LOG*. OSL_TRACE directs it output to the console. In non-product builds (--enable-dbgutil during configure), or when a particular file is compiled with debug, OSL_TRACE effectively expands to printf, otherwise it is a no-op. > How should that combination be pressed? Alt, then add Shift, then add Control > and the D > key? Or one by one in sequence? All at the same time. Ciao Frank -- ORACLE Frank Schönheit | Software Engineer | [email protected] Oracle Office Productivity: http://www.oracle.com/office --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
