https://bugs.freedesktop.org/show_bug.cgi?id=47044
--- Comment #16 from Stephan Bergmann <[email protected]> 2012-06-06 06:07:06 PDT --- (In reply to comment #15) > (In reply to comment #11) > > This should produce a number of debug output lines prefixed with > > "WinInetBackend" when opening "Tools - Options... - Internet - Proxy" (via > > OutputDebugString, so should be visible when running within WinDbg, or > > profiling from depends.exe, etc.). > > If you can make available that debug output, that should help us track down > > this problem. > > Any instructions how to setup console debug output on Windows? When running > this build I do not see anything like that. I used --enable-debug to build it. The output does not go to stdout/stderr (aka "console"), but is instead handed to Windows' OutputDebugString function. At least when attached to the soffice.bin process via a debugger, this output should be made available via that debugger. (For example, I tested this with the freely available depends.exe, <http://www.dependencywalker.com/>, loading soffice.exe into it and then "Profile - Start Profiling...", taking care that "Log debug output messages." and "Automatically open and profile child processes." are both checked, should start soffice.exe, which in turn starts soffice.bin, for which depends.exe then automatically opens a new sub-window, where the relevant debug output should appear in the bottom pane, along with other logging messages. If only Windows made debug output available in a straightforward way...) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
