Solved C4DUnhandledExceptionFilter - debugging log ?

nicholas_yue

I am troubleshooting a crash in C4D R21 commandline.exe on Windows 10

Error: application crashed
C4DUnhandledExceptionFilter: writing exception info
C4DUnhandledExceptionFilter: writing call stacks

Where are the likely place I can go to look at the exception info and call stacks that was being written out ?

Cheers

ferdinand

Hello @nicholas_yue,

thank you for reaching out to us. You can find the crash reports of Cinema in its preference folder. The preference folder should be located in \{USER}\AppData\Roaming\MAXON\{VERSION}\. It can also be opened via a button at the bottom of the preferences menu.

However, this will lead you to the preference folder of the Cinema 4D app, not the one for commandline.exe. The last element in the path will be a folder with a name like S24_XXX_YYYYYYY where the XXX part is the minor revision and the YYYYYYY part a hash with no higher meaning for the user. So, the path is then for example {USER}\AppData\Roaming\MAXON\S24_037_DFA0E3FB. When you have run the command line app at least once, then there will also be a folder with almost the same path, but only that an _x has been appended, e.g., {USER}\AppData\Roaming\MAXON\S24_037_DFA0E3FB_x. This path then contains all the commandline.exe data, including the bug reports, which should be visible to you under {USER}\AppData\Roaming\MAXON\{VERSION}_x\_bugreports. For testing purposes, you can always invoke a crash on Cinema 4D by using the argument -crashtest. So, .\Commandline.exe -crashtest will force a crash which should pop up in your {USER}\AppData\Roaming\MAXON\{VERSION}_x\_bugreports.

Cheers,
Ferdinand

ferdinand

Hello @nicholas_yue,

thank you for reaching out to us. You can find the crash reports of Cinema in its preference folder. The preference folder should be located in \{USER}\AppData\Roaming\MAXON\{VERSION}\. It can also be opened via a button at the bottom of the preferences menu.

However, this will lead you to the preference folder of the Cinema 4D app, not the one for commandline.exe. The last element in the path will be a folder with a name like S24_XXX_YYYYYYY where the XXX part is the minor revision and the YYYYYYY part a hash with no higher meaning for the user. So, the path is then for example {USER}\AppData\Roaming\MAXON\S24_037_DFA0E3FB. When you have run the command line app at least once, then there will also be a folder with almost the same path, but only that an _x has been appended, e.g., {USER}\AppData\Roaming\MAXON\S24_037_DFA0E3FB_x. This path then contains all the commandline.exe data, including the bug reports, which should be visible to you under {USER}\AppData\Roaming\MAXON\{VERSION}_x\_bugreports. For testing purposes, you can always invoke a crash on Cinema 4D by using the argument -crashtest. So, .\Commandline.exe -crashtest will force a crash which should pop up in your {USER}\AppData\Roaming\MAXON\{VERSION}_x\_bugreports.

Cheers,
Ferdinand