> I am using Cygwin on Windows to compile Yeah, but the actual compiler you are using is Microsoft's "Visual Studio 2008" surely. If you didn't know this, I am a bit surprised that you managed to build OOo.
(Don't be mislead by the "Visual Studio" name; that is the name of the whole product, which contains both the underlying command-line tools and an IDE, confusingly also called "Visual Studio". When building OpenOffice.org on Windows, the build uses the command-line tools from Visual Studio. The C and C++ compiler command is cl.exe for instance, and the linker is link.exe.) > and build the code. Are "gdb" and "C++ Builder" good options ? No. As you use Microsoft's compiler, you must use Microsoft's debugger. The Visual Studio IDE can be used just fine to debug OpenOffice.org code on Windows. You need to build the parts you want to debug for debugging, though. Typically you would start OOo and then attach the running soffice.bin process from the Visual Studio IDE. See the wiki for details. (At least, I hope there are details in the wiki...) > Would it involve loading all the files into the debugger or just the exe > file (scalc.exe for the sc project) ? You apparently are missing that scalc.exe (and swriter.exe, and soffice.exe, etc) is just a small helper executable that runs the actual OpenOffice.org executable, which is called soffice.bin. (Yeah, the ".bin" suffix is a bit strange. That's the way OOo is...) The same soffice.bin is used for all the "aspects" of OOo: Writer, Calc, Impress etc. Only one soffice.bin process is running at a time. --tml --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
