When I launch an executable that resides inside my Boxcryptor volume, Boxcryptor crashes: the volume is unmounted and Boxcryptor.app is unaware, which hence manually needs to be quit and restarted.
This does not happen for a simple "hello world"-executable compiled with c, but it happens for larger executables. One reproducible case is when I copy g++ into my volume and launch it, e.g.:
cp /usr/local/bin/g++ .
PS. (sorry for change of topic) I would like to attach a debug report, but what's with all the keys in there? Are they hashed, and can I be sure that my keys are not exposed when I send that report? Also, why aren't my paths anonimized in these reports?