Log any errors before cancel_init()

[Santti4go]

This PR improves the debugging process by adding a proper logging right before running SecurityManager::cancel_init() in this catch block

Description

More details in this ticket #5531

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.x

Fixes #(issue)

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• NA Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• NA Any new/modified methods have been properly documented using Doxygen.
• NA Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
• Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• Changes are API compatible.
• NA New feature has been added to the versions.md file (if applicable).
• NA New feature has been documented/Current behavior is correctly described in the documentation.
• Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• If this is a critical bug fix, backports to the critical-only supported branches have been requested.
• Check CI results: changes do not issue any warning.
• NA Check CI results: failing tests are unrelated with the changes.

[EugenioCollado]

Hi @Santti4go, thank you for creating this PR. As this change is compatible with the latest version and this branch is out of its End of Standard Support Date, we would appreciate it if you could rebase your commits onto the branch master and then we would backport it to the supported branches.

[Santti4go]

@EugenioCollado thanks for reviewing this.
I just made the requested changes.
Do you want me to add anything in the PR desc in order to enable backport?

[EugenioCollado]

LGTM

[EugenioCollado]

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.x

[mergify]

backport 3.1.x 3.0.x 2.14.x 2.10.x

✅ Backports have been created

• #5544 Log any errors before cancel_init() (backport #5530) has been created for branch 3.1.x
• #5545 Log any errors before cancel_init() (backport #5530) has been created for branch 3.0.x
• #5546 Log any errors before cancel_init() (backport #5530) has been created for branch 2.14.x
• #5547 Log any errors before cancel_init() (backport #5530) has been created for branch 2.10.x

[Mario-DL]

I think that the log macro should have been changed to EPROSIMA_LOG_ERROR() instead of the old one logError in master, as this would only build if ENABLE_OLD_LOG_MACROS is ON (by default). In addition, a proper test would have also been interesting.

[EugenioCollado]

I think that the log macro should have been changed to EPROSIMA_LOG_ERROR() instead of the old one logError in master, as this would only build if ENABLE_OLD_LOG_MACROS is ON (by default). In addition, a proper test would have also been interesting.

I will take care of the changes you mention in a new PR and will also include them in the already created backports