Tizen调试器消息:无法使用GDBClient启动应用程序

Question

我正在为我的混合应用程序开发一个API4.0版本的。在成功编译了应用程序之后，为了跟踪应用程序崩溃的原因，当我在模拟器W-4.0-循环-x86-预览上启动它时，它会在调试模式中给出一个错误消息。

错误消息：

Cannot launch application with GDBClient.

Error in final launch sequence

Failed to execute MI command:

source G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug\.gdbcommand

Error message from debugger back end:

G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug\.gdbcommand:5: Error in sourced command file:\nG:Computer ScienceApp DevelopmentMyAppGalaxyWatchAppMyAppNative ServiceDebugMyAppservice: No such file or directory.
G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug\.gdbcommand:5: Error in sourced command file:\nG:Computer ScienceApp DevelopmentMyAppGalaxyWatchAppMyAppNative ServiceDebugMyAppservice: No such file or directory.

GDBCommand文件内容：

set sysroot C:\Tizen\TizenStudio\tizen-studio\platforms\tizen-4.0\wearable\rootstraps\wearable-4.0-emulator.core
set debug-file-directory C:\Tizen\TizenStudio\tizen-studio\platforms\tizen-4.0\wearable\rootstraps\wearable-4.0-emulator.core\usr\lib\debug
set solib-search-path G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug
dir C:\Tizen\TizenStudio\tizen-studio\platforms\tizen-4.0\wearable\rootstraps\wearable-4.0-emulator.core\usr\src\debug
file "G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug\MyAppservice"
sharedlibrary

在网络搜索过程中，我发现了一些GDBClient错误，但是找不到这个错误的解决方案。

我还尝试将GDB Debugger的路径设置为i386-linux-gnueabi-gdb-7.8，将GDB Command File设置为应运行的.gdbcommand的绝对路径。

Answer 1

看起来问题就在于这一行：file "G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug\MyAppservice"

尝试从目录名中删除空格。将Computer Science改为Computer_Science，将App_Development更改为App_Development。然后右键单击项目并转到Debug As -> Debug Configurations...，然后删除活动调试配置并再次创建新配置。

您还可以尝试手动从file "G:\Computer Science\App Development\MyApp\GalaxyWatchApp\MyApp\Native Service\Debug\MyAppservice"文件中删除整行.gdbcommand，并检查它是否修复了问题。