Hello David,
Hello Raymond,

On 17.12.2013 23:31, Steele, Raymond wrote:
At long last Raymond and I have successfully gotten through the entire build 
script without a fault. The executable seemed to create just fine and we were 
able to launch soffice. We got the splash screen, then the executable started 
and the options window appeared and everything looked to be in order,

That's a great success!

but when we selected one of the document types to open, the executable crashed 
with the memory error:

./soffice[121]: wait: 6980: Memory fault

I'm afraid we need a stack trace of this crash to understand what's going on. When the stack trace shows which libraries are involved then these libraries should be recompiled with debug infos (i.e. created with the "debug=1" option for "make" or for "build"). Then replace the libs in your installation with the debug libs and get the stack trace of this crash.

I don't think Raymond or I was expecting everything to work right on first 
launch and we were happy to see the splash screen, the executable start and the 
option menu appear. However, have you seen this type of memory error before or 
has it been seen by others? Do you have an idea what might cause this?

If you single stepped through the huge amounts of code that is needed to get to there you'd see there is more than plenty of opportunity for something to go wrong ;-)

My fear is that we have made too many modifications to the code in order to get the 
system to build correctly. We have removed, in small select areas, "const" as a 
qualifier to certain parameters to member functions because the system would not compile 
with these parameters declared as a const. We can provide a list of these locations that 
we have edited, I believe it is about 3 or 4 files that might have been edited in this 
way.

The changes in the few source files you mentioned in your other mail are probably uncritical. And e.g. Calc isn't changed at all, so if it doesn't work either then I suspect the problem in a deeper layer.

If you have any ideas, it would greatly help us out. Thanks.

The stack trace of the crash when debug-enabled libraries were used would be very helpful

Herbert

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to