Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi Ashod,

Ashod Nakashian schrieb:

On Sun, Aug 30, 2015 at 8:39 AM, Regina Henschel
<rb.henschel@t-online.de <mailto:rb.henschel@t-online.de>> wrote:

    Hi David,

    David Tardon schrieb:

        So it is a segfault, not a unit test failure... Could you get a
        stack trace?


    I think no. I have never done it. I would need a step-by-step
    description for dummies.


Regina, you can debug in visual studio using the following command:

CPPUNITTRACE="\"C:/Program Files (x86)/Microsoft Visual Studio
12.0/Common7/IDE/devenv.exe\" /debugexe" /opt/lo/bin/make <test_name>

You need to correct the path to devenv and find the test_name that is
failing. You should find it near the end of the output. They all start
with 'CppunitTest_'.

When you run the above command, it will run the failing unittest from
within visual studio, which will break when it crashes. This will give
you an opportunity to inspect the stack trace (from the stack debug
window) and also see the code and line where it faults (if inside LO
codebase).

Let me know if you need more help.

I was more bravely now and have clicked on "start" in Visual Studio. Then a command window opened and therein I get http://pastebin.ca/3138849
Then it stops with the error message:
Unhangled exception at 0x0229B9A1 (vcllo.dll) in cppunittester.exe:
0xC0000005: Access violation writing location 0x00000004.

I have pressed "Bread".

And now?

Kind regards
Regina



Context


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.