Herbert, Raymond and I are in the process of rebuilding OpenOffice with the debug flags, but have run into some errors that didn't occur the first time through in the build. The current error has caused me quite a bit of problems.
We are getting a link error, unrecognized symbol in /svx/source/engine3d/e3dundo.cxx. However the symbol that it is looking for is not present inside e3dundo.cxx. The symbol is "ParagraphData&ParagraphData::operator=(const ParagraphData&)" [sic] which we have located in /editeng/inc/editeng/paragraphdata.hxx and the implementation appears to in /editeng/source/outliner/paralist.cxx. There are some very odd things going on here. 1) paragraphdata.hxx is not included in paralist.cxx even though this is where the prototype is declared. 2) e3dundo.cxx doesn't seem to use the ParagraphData class at all. 3) e3dundo.cxx doesn't seem to include the libraries where these classes are used. I want to note that we first started the debug build using multiple processors (-P8) and perhaps that has caused problems in the ordering in which the libraries were compiled and linked. It is conceivable that this problem may be resolved with a complete system clean and rebuild in linear mode, but before we committed to another day of building the product, we wanted to check with you to see if this problem has occurred before, is it recognized or if there is a solution that you could recommend? We'd appreciate any help or insight you could provide. David Meffe P.S. I will be on holiday for the next two weeks and I believe Raymond will be as well so we may be out of communication. -----Original Message----- From: Herbert Duerr [mailto:h...@apache.org] Sent: Wednesday, December 18, 2013 12:11 AM To: dev@openoffice.apache.org Cc: Steele, Raymond; Meffe, David K Subject: Re: EXTERNAL: Re: Building comphelper 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
