Community
Participate
Working Groups
given the use of cache in edc to improve performance, there are times the cache gets stale and prevents the user from seeing correct data. e.g. persistent NoFileCache sometimes prevents user from seeing files added after 1st attempt to view. Modules.java accesses and builds a "noFileCache" in the EDCDebugger.getDefault().getCache() location. The use case that causes a problem is 1) import an executable whose source is from another machine (particularly from another drive on another machine) 2) attempt to access the source during a debug session (with breakpoints or stepping) 3) creating a directory and perhaps a SUBST drive on windows that recreates the original source location. at this point, the no file cache may contain symbolics file of interest, and even though the file wasn't there the first time it was debugged, the user has made it available outside of edc, but edc's NoFileCache is preventing it from being seen.
(this is part of a batch change) The Eclipse CDT EDC (https://wiki.eclipse.org/CDT/cdt-debug-edc) is now obsolete and has not had any active development since 2011. Therefore the still open bugs are being marked as wontfix. The git repo for the project still exists for posterity at https://git.eclipse.org/c/cdt/org.eclipse.cdt.edc.git/
