Today I tried to execute every samples provided with the DriveWorks SDK. All was going well.
But when I tried to execute the sample_drivenet file, this one was crashing after 2s and also crashing my computer (which rebooted).
The command I used on Linux to run it looks like:
./sample_drivenet --video=<rccb.raw> --stopFrame=0.
The only .raw video file provided with the SDK being very short (max 0.5 second of video), I though the crash was due to an excessive looping of this one (the --stopFrame flag provided being 0). So I changed my command into:
./sample_drivenet --video=<rccb.raw> --stopFrame=1.
to play only one frame of video and prevent it from looping very quickly. Still, the video kept lopping very quickly in the display window (3 or 4 time before crash). And from what I had the time to see before my computer shut down, the DriveNet recognition wasn’t occurring.
=> 1: How can I get the console error message, given that the entire computer crash before I even have the time to read more than a single line in the console ?
=> 2: Can it be due to a CPU overcharge ?
=> 3: Can it be due to a GPU orvercharge ?
=> 4: Can it be due to a RAM overcharge ?
(NB: I also tried it with a .h264 video, for the same result, but the drive net recognition was working before the crash)