Re: [Libreoffice] Build issue with cppu

Caolán McNamara <caolanm -AT- redhat.com>
Tue, 25 Jan 2011 16:27:06 +0000

On Tue, 2011-01-25 at 21:00 +0530, Surendran Mahendran wrote:

Hi Dave,

On 01/25/2011 02:20 PM, David Tardon wrote:


Run

build -- debugcppunit=t

. This will run the test through gdb and create qa/gdbtrace.log that
you can post here.

D.


Thanks for the tip. I have pasted the gdbtrace.log in the pastebin [1].
This seems to be the problem -


Hmm, well it doesn't fail here FWIW. Could you autogen.sh with an extra
--enable-symbols and rm -rf cppu/unxlngx.pro and redo the trace so we
can get the exact line numbers to see if its e.g. the very first
try/catch in testUnoSetThrow or some other one.

C.

Context

[Libreoffice] Build issue with cppu · surenspost -AT- gmail.com
- Re: [Libreoffice] Build issue with cppu · David Dumaresq
  - Re: [Libreoffice] Build issue with cppu · surenspost -AT- gmail.com
    - Re: [Libreoffice] Build issue with cppu · Jonathan Aquilina
    - Re: [Libreoffice] Build issue with cppu · David Tardon
      - Re: [Libreoffice] Build issue with cppu · Michael Meeks
      - Re: [Libreoffice] Build issue with cppu · Surendran Mahendran
        
        Re: [Libreoffice] Build issue with cppu · Caolán McNamara
        
        Re: [Libreoffice] Build issue with cppu · Surendran Mahendran
        
        Re: [Libreoffice] Build issue with cppu · Caolán McNamara
        Re: [Libreoffice] Build issue with cppu · surenspost -AT- gmail.com

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.