When a Print statement is used in an “On Error GoTo” catch routine, the information in Err, Erl, and Error is not reliable in some cases; for example, this can be reproduced when errors are generated by the Simple File Access object's getFolderContents() method. The Print statement appears to display error information from prior errors not the current error. This occurs in both Linux and Windows environments. It is not clear if this is limited solely to an interaction with the Print statement or if there are other ways in which this bug can surface. It is not clear why the Print statement behaves in this manner and does not print all of the information associated with the current error.
Steps to reproduce:
This is reproducible by catching errors from the “getFolderContents()” method. This appears to generate two additional errors internal to LibreOffice for a total of three errors to be printed. Only two are printed. After the first such error, the Catch routine falls further and further behind, which is very confusing for any attempts at understanding or debugging (see 3.1, “Results with Debug Level > Zero“ for more information).
Current behavior: Incorrect information is displayed for Error, Erl, and Err.
This also leads to unexpected output at the end of the program execution (see Illustration 2: Unexpected output at the end of program execution and Table 5: Result summary for Linux, getFolderContents() method for more information)
Caught errors should generate all output conurrent with the error event.
I will upload a separate document with screen shots and supporting documentation.
Operating System: All
Version: 220.127.116.11 release
Created attachment 98561 [details]
Screen shots and additional notes to reproduce problem
This has been unconfirmed for 2,5 years, because there is no test document to easily reproduce the issue.
Please attach such a document, your steps to repro are not clear enough. Testers should not have to think. You should view us as trained monkeys.
status NEEDINFO as per previous comment
retest with latest LibO 18.104.22.168
if bug is gone set status to WORKSFORME
if bug persists provide testcase and set it back to UNCONFIRMED
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker