Created attachment 99860 [details] strace.log When I call "/opt/libreoffice4.2/program/soffice '--accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager' --nologo --headless --nofirststartwizard" it crashes with exit code 134 with no output errors. The uname -a output is: Linux myhostname 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT 2008 i686 i686 i386 GNU/Linux The x86-64 version works fine, the issue is on i386. They are all VMs in a VmWare Server. Please, let me know if there is more info that I can provide for identify/solve the issue.
Sergio: would it be possible you retrieve a backtrace by following this link? https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Created attachment 99920 [details] backtrace log Of course, but I can't find the distribution package of libreoffice-debuginfo for the CentOS version and its not provided at the LibreOffice_4.2.4.2_Linux_x86_rpm/RPMS/* downloaded from libreoffice.org... I've generated de backtrace log file without the debugging library, if you need it let me know, please. Thanks!
Sergio: I just googled "libreoffice debug centos" and found this, http://pkgs.org/centos-6/russian-fedora-free-updates-i386/libreoffice-gdb-debug-support-3.5.1.2-1.el6.R.i686.rpm.html Could you confirm a package named with the prefix "libreoffice-gdb-debug-support"? Also for the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and give it a new try?
Created attachment 100078 [details] backtrace with profile directory removed before execute the process
Profile dir removed before executing the process and nothing happened... The package libreoffice-gdb-debug-support is not on the libreoffice distribution RPMS directory: http://donate.libreoffice.org/home/dl/rpm-x86/4.2.4/es/LibreOffice_4.2.4_Linux_x86_rpm.tar.gz and it should be generic for RPM based distros. "yum search libreoffice* | grep debug" doesn't returns output, so I cannot find nothing like debug for libreoffice. Thank you.
Just by curiosity, how did you install 4.2.4 version? Via Yum or by downloading in LibreOffice website? For the test, could you give a try to a daily master build with debug info? See http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@45-TDF-dbg/current/ With dbg info, the precise line where it crashes should be pinpointed.
Created attachment 100149 [details] backtrace log from dev version
Hi Julien, At first, I installed libreoffice from the website link of my last comment to install the latest version. Now, I've erased the last version and installed the dev version from your link. The log looks a little criptic for me... Thank you!
Thank you Sergio for your feedback. Weird indeed, your bt shows this: #4 0x003dbf02 in xmlreader::XmlReader::XmlReader (this=0x80b3fe8, fileUrl=...) at /home/buildslave/source/libo-core/xmlreader/source/xmlreader.cxx:111 #5 0x03257a5f in configmgr::ParseManager::ParseManager (this=0x80b3fe0, url=..., parser=...) at /home/buildslave/source/libo-core/configmgr/source/parsemanager.cxx:40 but xmlreader.cxx:111 correspond to the end of the constructor (see http://opengrok.libreoffice.org/xref/core/xmlreader/source/xmlreader.cxx#111). Since I don't have more question and there's a backtrace, I put it to NEW Riccardo: since it concerns headless stuff, one for you?
Hi, Did you see something with the backtrace of the development distribution? Thank you!
(In reply to comment #9) > Thank you Sergio for your feedback. > > Weird indeed, your bt shows this: > #4 0x003dbf02 in xmlreader::XmlReader::XmlReader (this=0x80b3fe8, > fileUrl=...) at > /home/buildslave/source/libo-core/xmlreader/source/xmlreader.cxx:111 > #5 0x03257a5f in configmgr::ParseManager::ParseManager (this=0x80b3fe0, > url=..., parser=...) at > /home/buildslave/source/libo-core/configmgr/source/parsemanager.cxx:40 > > but xmlreader.cxx:111 correspond to the end of the constructor (see > http://opengrok.libreoffice.org/xref/core/xmlreader/source/xmlreader. > cxx#111). > > Since I don't have more question and there's a backtrace, I put it to NEW > > Riccardo: since it concerns headless stuff, one for you? It doesn't look anything headless specific. One interesting thing could be sorting out the actual file that crashes ParseManager and attach it to this bugreport.
Hello Riccardo, What do you need exactly? Thank you.
(In reply to comment #12) > Hello Riccardo, > > What do you need exactly? #4 0x003dbf02 in xmlreader::XmlReader::XmlReader (this=0x80b3fe8, fileUrl=...) at /home/buildslave/source/libo-core/xmlreader/source/xmlreader.cxx:111 Getting the file the fileUrl variable points to.
Hello Riccardo, The backtrace shows "..." for the variable values. How can I retrieve that information? Thank you.
Hello, First at all, thank you for the help. Do you have any ideas that how can I retrieve the XML that makes the application crash? Regards.
(In reply to comment #15) > First at all, thank you for the help. > Do you have any ideas that how can I retrieve the XML that makes the > application crash? We have some fine documentation over here: https://wiki.documentfoundation.org/Development/How_to_debug There's no need to ping every week or so.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Message generated on: 10/01/2015
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-02-11