Question
I'm encountering an issue when trying to debug an application in the Tizen Emulator using Visual Studio 2017. The Visual Studio output window shows that it cannot find some .NET Core files and then exits sdb.exe.
Example output:
Terminal Output
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.4/System.Private.CoreLib.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.4/SOS.NETCore.dll'. Cannot find or open the symbol file.
...
The program 'sdb.exe' has exited with code 0 (0x0).
The application compiles and installs successfully, but when the debugging process starts, sdb stops and the application never launches. However, if I install the app directly from the Tizen sdb Command Prompt, I can run it (but not debug it).
Environment:
- Visual Studio 2017 (version 15.9.11)
- Windows 10
- Tizen 5.0 Emulator
- TV Extension Image 5.1.0
What could be causing this issue?
Answer
Problem Understanding
The issue occurs specifically when:
- Debugging OpenGL applications (like JuvoPlayer's OpenGL version)
- Using Visual Studio's debug mode (Ctrl+F5 works)
- The application runs fine when installed via sdb command line
Solution Methods
-
Verify Tizen Studio Installation:
- Ensure you have the latest Tizen Studio version (broken SDK installer was fixed on July 29th)
- Check if all required components are properly installed
-
Certificate Configuration:
- Create a partner certificate
- Grant emulator permissions to install apps
- Configure Visual Studio to use the correct certificate (Tools → Options → Tizen)
-
Debugging Workarounds:
- Try running without DllImport (which might not be supported by the debugger)
- Use "Start without Debugging" (Ctrl+F5) as a temporary workaround
Additional Tips
- The "Cannot find or open" messages appear to be related to symbol files and might not be the root cause
- Focus on the specific OpenGL debugging scenario as this seems to be the trigger
- Consider testing with simpler applications to isolate the issue
