Description: (sal/rtl/strimp.cxx) rtl_allocateStringFn rtl_allocateString = malloc; is initialized after const OUString BACKSLASH ("\\"); (sal/osl/w32/path_helper.cxx), so it calls 0 address during dll initialization. Steps to Reproduce: I'm doing custom builds (not wiki workflow) on VS2019. So, the first target to build is sal, then codemaker and it does not start because of this issue. Actual Results: Error during globals initialization by CRT (before main call). Expected Results: Must work. Reproducible: Always User Profile Reset: No Additional Info:
Hello, Since this is build issue and not a software issue, would you mind sending an email to the dev list instead? -> https://wiki.documentfoundation.org/Development/Mailing_List Closing as RESOLVED MOVED
See possible fix https://gerrit.libreoffice.org/#/c/70483/
ok, assigning it to you. Thanks for the patch ;-)
Patch restored in gerrit
Hi Egor, Are you still working on this issue? Please see comment from 2019-04-11 in https://gerrit.libreoffice.org/#/c/70483/. Setting to NEEDINFO meanwhile
Hi, No, I'm not working on this, don't have enough time. Bug is reported, you know about it. Code owners should know how to fix this better.
Code is 30 years old. difficult to tell who is the code owner...
Dear Egor Pugin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug