Bugzilla – Full Text Bug Listing
| Summary: | GDB Hardware Debugging environment variables | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Paul McConkey <paul.mcconkey> |
| Component: | cdt-debug-cdi-gdb | Assignee: | cdt-debug-inbox <cdt-debug-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Paul McConkey
The environment variables in the Debugger settings apply the target implementation, not the debugger. Other than the path to GDB, which other environment changes do you need? For the MinGW integration, I found using the full path to GDB sufficient. OK, I see the problem, there would have to be environment variables for two contexts - the debugger and the target. My GDB 'target remote' command refers to a stub executable which GDB can only find if the folder containing the stub is added to the PATH environment variable. It may be as well to leave it lke this rather than complicate the issue. However, when researching this, I noticed that the environment variables are sent to the debugger after the Hardware debugger plugin sends the load command, which also means that the Image file name has to be specified with a full path, rather than than one relative to the project folders. Can this be changed? after many years the problem i still present, I proposed a patch for cdi and dsf https://bugs.eclipse.org/bugs/show_bug.cgi?id=338418 https://bugs.eclipse.org/bugs/show_bug.cgi?id=338420 (this is part of a batch change) The CDI debug implementation has been removed in CDT 9.0. Please see bug 484900 and the entry on the New and Noteworthy page https://wiki.eclipse.org/CDT/User/NewIn90#API_modifications |