SourceForge has been redesigned. Learn more.
Close

#48 Support for project-less debugging

Time Permitting
closed-fixed
None
5
2014-07-12
2014-05-21
John Moule
No

Since CDT 8.0 the feature referred to as projectless (project-less) debugging has been supported:

https://wiki.eclipse.org/CDT/User/NewIn80#Project-less_debugging

Using default values the Segger and Openocd launch configurations do not support projecless debugging. This is because the "GDB client setup > Executable " uses a value of ${cross_prefix}gdb${cross_suffix}. These variables are defined on a project level. If no project is specified then those variables are not defined.
A workaround to this is to use an absolute path.

However, if the user defined those variables in the workspace build variables (Window > Preferences > C/C++ > Build > Build Variables) then the launch would work without a project being specified.

I propose a change to:

ilg.gnuarmeclipse.debug.gdbjtag.jlink.Utils.getLaunchEnvironment(ILaunchConfiguration)

where if the project is null or empty then the workspace build variables are returned, rather than null at the moment.

I could have a go at providing a patch for this if I can figure out how to get the workspace build variables.

cheers john

Discussion

<< < 1 2 (Page 2 of 2)
  • Liviu Ionescu (ilg)

    ok, then tomorrow we'll have a new public release.

     
  • Liviu Ionescu (ilg)

    • status: open-accepted --> closed-fixed
     
  • Liviu Ionescu (ilg)

    fixed in 2.3.1-201407120554

     
<< < 1 2 (Page 2 of 2)