Thanks Tor,
I success debug with Attach to process solution but I want to debug the code
that execute when LibO start. Attach to process can only debug after LibO
already started. How can I debug the startup code in VCL?
How can I debug soffice.bin? Any environment variable that I need to set.
Thanks Tor,
It's work.
On Mon, Feb 7, 2011 at 3:33 PM, Tor Lillqvist tlillqv...@novell.com wrote:
I success debug with Attach to process solution but I want to debug the
code
that execute when LibO start.
Ah. That is always hard for me because
1) I never remember which source file it
FYI: We simply rename soffice.bin to soffice.bin.exe and open in it Visual
C++. Then add those path you mentioned in Project Properties.
Thanks.
On Mon, Feb 7, 2011 at 4:56 PM, Tantai Tanakanok tan...@osdev.co.th wrote:
Thanks Tor,
It's work.
On Mon, Feb 7, 2011 at 3:33 PM, Tor Lillqvist
On Mon, 2011-02-07 at 17:05 +0700, Samphan Raruenrom wrote:
FYI: We simply rename soffice.bin to soffice.bin.exe and open in it
Visual C++. Then add those path you mentioned in Project Properties.
Sounds like we need to add this to some how to debug LibreOffice wiki
page :-) [ neat tip
Hi all,
I have a problem when I was debug LO with Visual C++ 2008. My step to debug
is:
1. build the module(vcl) with debug=true and copy dll file to LO
Installaion directory/program.
2. start Visual Studio and open exe with File Open Project/Solution
and choose soffice.exe in
2. start Visual Studio and open exe with File Open Project/Solution
and choose soffice.exe in program folder.
It is not soffice.exe that is the actual LibreOffice program, it's soffice.bin.
(Which despite its odd .bin suffix is a totally normal .exe file.) Soffice.exe
is just a thin
