Hi - > On Oct 28, 2017, at 10:30 AM, Patricia Shanahan <[email protected]> wrote: > > The original bug report said "This wasn't an issue of AOO 4.1.3, but is an > issue of AOO 4.1.4" so we are looking for something that changed. > > I would have assumed that the same libraries would be used in writing the > main content.xml and the one in the 'Object 1' subdirectory. The main > content.xml is fine. The one in the 'Object 1' subdirectory is empty, so I am > confused and puzzled. > > Can someone with Mac building and testing capability do the search for the > change that made it fail? In another project, I used binary search on the SVN > revision number to locate exactly when a regression appeared.
I think that only Jim can build 4.1.4 on Mac. I am blocked waiting for a friend to give me a Mac JDK7. Or, I’ll apply Damjan’s javadoc JDK8 patches and see. Keep in mind that 4.1.3 was built over a year ago. AFIAK it was not built by Jim. Apple has updated Xcode and switched MacOSX to macOS since then. We ought to factor out the build tooling by comparing a build based on 4.1.3 with the bug to rule out a tooling regression. > > (For anyone who is not already familiar with the structure of the files, it > may be useful to look at an unzipped .ods file.) Regards, Dave > > On 10/28/2017 10:01 AM, Dave Fisher wrote: >> Hi - >> I’ve attached a diff of the differences between 4.1.3 and 4.1.4. I hope that >> this helps. If I had a working build I would be looking into undoing a >> change at a time to see which had the impact on the save of links on Mac. >> I am also suspicious of tooling and what caused the link xml to be created, >> but empty. Is there a system library involved and an impact due to fixes and >> updates in Xcode? If aoo413 is built on the same tooling as aoo414 is it >> broken too? >> Regards, >> Dave >>> On Oct 28, 2017, at 5:47 AM, Patricia Shanahan <[email protected]> wrote: >>> >>> I at first thought this might be a load problem. It is now clear it is a >>> case of file corruption on save, only on Mac. >>> >>> Unfortunately, that means I am out of ideas, other than checking that your >>> original test has been done on the file save. The fixes I know about are >>> intended to affect file loading, not saving. >>> >>> On 10/26/2017 5:45 AM, Jim Jagielski wrote: >>>> Yeah, I kinda figured out what your hypothesis was... I'll need >>>> to think about this some more. >>>>> On Oct 26, 2017, at 8:34 AM, Patricia Shanahan <[email protected]> wrote: >>>>> >>>>> OK, forget that hypothesis. You have even done the next test I would have >>>>> asked for if the line 288 breakpoint was not reached. >>>>> >>>>> I'll need to think up a new hypothesis. I'm planning to go groom a couple >>>>> of horses this morning, but I'll work on this in the afternoon. >>>>> >>>>> On 10/26/2017 5:01 AM, Jim Jagielski wrote: >>>>>> I set breakpoints on both: >>>>>> (lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx >>>>>> --line 288 >>>>>> (lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate >>>>>> Breakpoint 4: where = >>>>>> libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), >>>>>> address = 0x000000010070a260 >>>>>> and when opening up the corrupted file, neither breakpoint >>>>>> was reached. :/ >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
signature.asc
Description: Message signed with OpenPGP
