Open KevinBalz opened 5 years ago
I've never used the debugger with the library before, and didn't have access to the debugger whilst developing it so I'm not sure why you're receiving a segmentation fault. There is a lot of interop going on with p/invoke so that might be the cause, especially when the native function pointers are called. Are you sure the Raspberry Pi supports debugging via visual studio? I know Windows IoT works fine but I'm not sure Linux support is as refined.
I don't think this is the fault of the library but more so debugging support on the Pi.
Debugging seems to work fine, setting breakpoint and stepping works without a problem until it hits cam.ProcessAsync
. Of course it's possible that there is a bug in the debugging tools itself, considering the library is likely to hit more edge cases through p/invoke etc.
I am experiencing very similar issue. @KevinBalz - have you managed to resolve it somehow, please?
When starting the code example below, and attaching the visual studio debugger over ssh, the program quits after ~2 seconds (due to 'Task.Delay`) with this output
When not attaching a debugger at all or attaching after
ProcessAsync
everything works as expected.