https://bugs.documentfoundation.org/show_bug.cgi?id=156842
Patrick Luby <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Assignee|[email protected] |[email protected] | |desktop.org --- Comment #9 from Patrick Luby <[email protected]> --- (In reply to Patrick Luby from comment #8) > I have no clue how the extended PDF is getting messed up (i.e. why is no > PDFWriter::Document extended PDF element ever added) so I would like someone > more familiar with this code to review my patch. Well apparently this messed extended PDF data also exists in a unit test and my change triggers that broken test PDF to now hit an assertion. Unassigning myself as I don't really have any idea how the extended PDF data gets so messed up so often. Apparently calling OSL_FAIL is "normal" and the code must create garbage data (which causes this bug) for the CppunitTest_vcl_pdfexport unit test to succeed. I still have no idea why in this bug and the CppunitTest_vcl_pdfexport unit test case there is no PDFWriter::Document attached to the root PDF extended data. Which code is supposed to set this? -- You are receiving this mail because: You are the assignee for the bug.
