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


On Sun, Aug 30, 2015 at 12:18 PM, Regina Henschel <rb.henschel@t-online.de>
wrote:

Hi Ashod,

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?

Great. You can now look at the stack where the exception happens.

Go to the Debug menu > Windows > Call Stack.

You can also use the many other tools to debug and find the root of the
problem.

But the stack is where you want to start. Try to find the first function
(from the top) that is within LO project.
Most likely the debugger stopped in a helper function that we don't care
about.

Double click on that function, and it should open the source code.
If it opens the disassembly window, just close it and double-click on the
function again (assuming you have the sources in the right place and the
function IS in our code, it should work).

Try to figure out the context by navigating (double click on function name
in stack) and see what variable has the unexpected value.

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.