On Thu, 2008-07-10 at 09:58 -0400, Terrence Enger wrote:
> Is there a `configure` option to turn this on?
There's a configure option to build with -g and to not strip the
libraries and binaries when delivering/installing, i.e. --enable-symbols
There isn't a configure option to create a distributi
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
Please let me second Joerg's request for a debuggable download.
My interest arises not from any mystery or suspicion of a problem in the
OOo code but simply from a taste for using an interactive debugger as a
tool for understanding the code. I think this habit is somewhat common.
Is it possible
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 o
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.
To build with debug info use "build debu
Hi,
in some cases it would be great to have an debugable version of an
OpenOffice.org release (e.g 2.x.x) to clarify problems. When using the
API of OOo (for example within an extension or an external
java program) and OpenOffice.org crashes under misterious circumstances
this could the best w
