Debug launch failure.

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Debug launch failure.

ソリューションへジャンプ
3,646件の閲覧回数
randenewberry
Contributor IV

We think we are having the problem described in the release notes under the Debugging section, item 4 (shown below)

Problem is I can not find where to point directly to the GDB exe (i.e. where is this setting "${cross_prefix}gdb${cross_suffix}")?

Can anyone help?

 

Thank you

 

Reference release note, Item 4:

ISSUE: If the PATH variable has double semicolons (;;) or a semicolon at the end, launching gdb debugger might fail. The it is possible that the gdb debugger specified with ${cross_prefix}gdb${cross_suffix} is not found. An error message with "Error while launching command: gdb --version" is shown.
WORKAROUND: The likely reason for this issue is a double semicolon in the PATH environment variable, or a semicolon at the end of the variable,  If a double semicolon or one at the end is present in your PATH, remove it. If this does not help: In the launch configuration settings, instead using ${cross_prefix}gdb${cross_suffix}, point directly to the GDB executable, e.g. "C:\Freescale\KDS_1.0\toolchain\bin\arm-none-eabi-gdb.exe".

ラベル(1)
0 件の賞賛
返信
1 解決策
2,527件の閲覧回数
randenewberry
Contributor IV

Hi Erich,

Making that change changed the error message, which led us to the problem: We did not select a Device Name..

Thank you for the assistance, we are in the debugger!

元の投稿で解決策を見る

0 件の賞賛
返信
3 返答(返信)
2,527件の閲覧回数
BlackNight
NXP Employee
NXP Employee

It is in the debug configuration. Use the menu Run > Debug configurations..

Then it is in the Debugger tab of your connection (see attached screenshot).

2,528件の閲覧回数
randenewberry
Contributor IV

Hi Erich,

Making that change changed the error message, which led us to the problem: We did not select a Device Name..

Thank you for the assistance, we are in the debugger!

0 件の賞賛
返信
2,526件の閲覧回数
randenewberry
Contributor IV

Hi Erich,

Thanks for the quick reply, we are trying it now, and let you know!

0 件の賞賛
返信