Thanks Tor,<div><br></div><div>It's work.<br><div><br><div class="gmail_quote">On Mon, Feb 7, 2011 at 3:33 PM, Tor Lillqvist <span dir="ltr"><<a href="mailto:tlillqvist@novell.com">tlillqvist@novell.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> I success debug with Attach to process solution but I want to debug the code<br> > that execute when LibO start.<br> <br> </div>Ah. That is always hard for me because<br> <br> 1) I never remember which source file it is that actually contains the "main" program of soffice.bin. There are half a dozen or so files with promising names and/or promising directory names... of course none of them has any comment giving a short descreiption of its purpose.<br> <br> 2) Once you figure out which file actually is the real main, you then need to build that stuff with debug=t, open the soffice.bin in VS (does VS like that, does it understand that it is a normal executable even if called .bin, don't know), and I guess set in the "project's" properties PATH so that it includes the URE/bin and Basis/program directories, and then just start it under the debugger.<br> <br> Occasionally I have found it easier to just add a "volatile int hang=1; while (hang);" loop in the main program or some other low-level enough function, once I find it, and start it normally and just attach soffice.bin in the debugger, break it, set breakpoints, set hang to zero, and continue...<br> <br> --tml<br> <br> <br> <br> </blockquote></div><br><br clear="all"><br>-- <br>_/|\_ Tantai Thanakanok. Open Source Development Co., Ltd.<br>Tel: <span><a>+66 38 311816</a></span>, Fax: <span><a>+66 38 773128</a></span>, <span><span><a href="http://www.osdev.co.th/" target="_blank">http://www.osdev.co.th/</a></span></span><br> </div></div>