This GCC issue doesn't affect the vanilla Hamburg Linux builds, but it may affect some distribution builds, depending on their version of gcc.
To test, load https://bugzilla.redhat.com/attachment.cgi?id=405919 and run the macro inside the .odt on x86. If it crashes inside osl_systemPathRemoveSeparator then you more than likely have a gcc which is affected by http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43560 The problem is that in x86 -Os mode gcc generates code that always writes back to the length member of the passed in rtl_uString even when it doesn't need to, i.e. a string of length 0 passed in has 0 re-written back to the length member. 0 length empty strings in OOo are optimized to always point to a single shared const empty string. And that const string is in the read-only section so a write back to it causes a SIGBUS. C. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
