AnsweredAssumed Answered

Debug launch failure.

Question asked by Rande Newberry on May 23, 2014
Latest reply on May 23, 2014 by Rande Newberry

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".

Outcomes