Problem to read .mat file when terminating a process

[kouroshD]

Hi,
I start using MatLogger in one of my projects.
When I terminate the process (ctrl+c) that uses matlogger, sometimes I get the following message before the process terminates:

libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

And in this case, I cannot read generated .mat file inside the matlab (even if its size is not 0 kb!)
And I suspect it is related t MatLogger, since before I did not have this error, and MatLogger is using mutex.
However, in other cases I have the following prints inside the terminal:

XBot::MatAppender::~MatAppender()
Flusher thread exiting.. Written 0.0 MB
Flushed all data for file 'myData.mat'

So, I wanted to know what is the correct way to close the logger, and finally call its destructor.
Do I need to flush the available data in YARP::RFModule::close method by calling flush_available_data()method? or I should use reset() method ?

Thank you.

[alaurenzi]

Hi, I am reading this with huge delay but... if you are still interested, you could provide me

• a backtrace obtained with gdb running a Debug build of MatLogger
• possibly, a minimum working example that I can compile and that shows (even sporadically) the issue

I know the latter could be a problem, but the first could really help

[kouroshD]

No problem with the delay :)
Unfortunately, I could not log the gdb output, since it was not supporting the latest version of macOS, and I did not try it recently. This problem was happening some times, not always, so I think it was related to memory management.
After I added the following line in the code, https://github.com/robotology/walking-teleoperation/blob/75169f6ecd71feb8a71f2428e23ac0eae18d0345/modules/Oculus_module/src/OculusModule.cpp#L426, I did not face the problem anymore.