Hello All, On Mon, Oct 13, 2025 at 09:03:27AM +0200, Arrigo Marchiori wrote:
> Hello Damjan, All, > > On Mon, Oct 13, 2025 at 03:01:33AM +0000, Damjan Jovanovic wrote: > > > On Sun, Oct 12, 2025 at 8:05 PM Arrigo Marchiori <[email protected]> wrote: > > > > > Hello All, > > > > > > I looked into the way expat is built and used in AOO. > > > > > > TL;DR: expat functions are partially taken from our expat, and > > > partially from system-level expat. > > > > [...] > > > > > > Why is the system-level libexpat.so calling internal functions of our > > > own statically linked expat? How can we avoid it? > > > > Try running AOO as: > > LD_PRELOAD=/path/to/system/libexpat.so soffice.bin > > > > Does that crash? > > I will try later from home. I tried on my openSUSE Leap 15.6 system at home, and I confirm it crashes. Function XML_ParserCreate_MM is resolved to the wrong .so library. But: if I set LD_PRELOAD=/path/to/system/libexpat.so as you suggested, then AOO starts and runs successfully. After it ran successfully, then on next runs, function XML_ParserCreate_MM is called from a secondary thread (probably something has changed in the configuration) and... it works! So, AOO only crashes until I manage to run it successfully _once_. Then it will always start successfully. > In the meantime, I fired up a VM with the lates OpenSUSE at work > and... it works well here! > > I could have done something wrong on my own system at home. I created another user on my system, and it shows the same behavior. I must try with a fresh install of openSUSE 15.6 to understand if it is a problem of my system or of that distribution in general. (I am reluctant to upgrade to openSUSE 16 because it does not seem to ship certain packages that are required for AOO development... more on this later). Best regards, -- Arrigo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
