Mike Kaganski
8ea8e254a3
It seems that both marshal_data and unmarshal_data are expected to take only non-null argument. Further, the checks were corrected: e.g., rtl_uString_release itself only takes a non-null argument, so *ppUnoStr must be checked before the call, not ppUnoStr. The static analyzer saw that ppUnoStr was checked if it was non-null; and was dereferenced later, outside of the check, unconditionally. The analyzer flagged that as a potential nullptr dereference. It was a useful warning, flagging the actual code problem. Unfortunately, our analyzer build in CI doesn't build DOTNET; I found this locally. Change-Id: I4bcbcd1ce8246835901c6032cae9e8b41a76dbf1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/191060 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
UNO Bridges
Bridges from various C++ ABIs, Java JNI, MS .NET to UNO and back. A bridge for .NET is in
cli_ure.
Also implementation of the UNO Remote Protocol.