After following the instructions mentioned at " Debugging Slicer application startup issues" I found the following error in the Start Event Viewer:
Nombre de la aplicación con errores: SlicerApp-real.exe, versión: 0.0.0.0, marca de tiempo: 0x5f17e3fa
Nombre del módulo con errores: ntdll.dll, versión: 10.0.18362.815, marca de tiempo: 0xb29ecf52
Código de excepción: 0xc00000fd
Desplazamiento de errores: 0x000000000003c43a
Identificador del proceso con errores: 0x5c
Hora de inicio de la aplicación con errores: 0x01d66086ddb40c79
Ruta de acceso de la aplicación con errores: C:\3DS\3DSR\Slicer-build\bin\Release\SlicerApp-real.exe
Ruta de acceso del módulo con errores: C:\Windows\SYSTEM32\ntdll.dll
Identificador del informe: b439a091-725a-425c-9c26-f1644ffd5c8e
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
Could you please build in debug mode and run it in a debugger? Then you can see exactly where the application crashes and why.
If the crash is not reproducible in debug mode then build it in RelWithDebInfo and run it in a debugger. Some symbols may be optimized out, but you should still find enough information about what went wrong.
Hello James, sorry here.
I posted an erroneous log. The posted log was from a test that I made changing the compatibility properties from the generated Slicer.exe.
After several hours in the building process, I finally accomplish the building in debug mode.
I needed to modify a little bit the files “archive_read_support_format_warc.c” and “archive_write_set_format_zip.c” at the LibArchive project, in order to have a successful build. The modification in both files was the same, specified all the options of the declared enums in the switch case statements when needed. Not specified all the options cause a C4061 Error.
So, after a successful build, the program runs without a problem in debug mode. At the moment I don’t know what is happening with the release build.
Thank you for the update, this is good progress. Since there is no crash in debug mode, you need to build and test in Release with debug info (RelWithDebInfo) mode as well.