On Wed, 2008-07-09 at 15:23 +0100, Caolan McNamara wrote: > On Wed, 2008-07-09 at 15:54 +0200, Philipp Lohmann wrote: > > non product build != debuggable build > > > > a non product build contains no more debugging information than the > > product build; the non product build activates assertions (per default > > in the form of popping up dialog boxes) which may or may not hint problems. > > > A build complete with debug info is possible on Windows I think, > > however on other platforms the libraries grow so much, that the office > > does not fit > > FWIW, what most linux distros do is to build a product version, so no > debugging assertions and so on. But a product version with symbols > enabled and then (as with other applications) the standard distro build > process extracts debuginfo into a separate rpm, leaving a stripped OOo > behind. And gdb and other tooling understands such separated debuginfo.
Is there a `configure` option to turn this on? > > So, for a sample DEV300_m23 that gives a 486Meg debuginfo package at > http://kojipkgs.fedoraproject.org/packages/openoffice.org/3.0.0/0.0.23.1.fc10/i386/openoffice.org-debuginfo-3.0.0-0.0.23.1.fc10.i386.rpm > and for what it's worth, in the case of fedora, the simple text report > spat out on a OOo crash can be symbol-ified with > http://people.redhat.com/caolanm/ooocvs/ooomapstack > which takes the backtrace from the stripped OOo and a matching unpacked > debuginfo and adds the symbols back in (regardless of prelink symbol > munging) > > In theory at least I guess that "vanilla" OOo could consider building > with symbols enabled and use the debuginfo tooling to extract the > debuginfo and keep it available for download for installation by the > dedicated. Or for those suffering from a terminal case of curiosity <grin />. Thanks, Terry. > > C. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
