Can you give an example for such output?brownhamer wrote:Unfortunately it does not solve the problem for me. The 'file' attribute from cygwin gdb contains the cygwin style filename as well.
Eran
Can you give an example for such output?brownhamer wrote:Unfortunately it does not solve the problem for me. The 'file' attribute from cygwin gdb contains the cygwin style filename as well.
This sounds like a valid direction + implementing a small cache for the file paths (which will be cleared on start/stop debug) can reduce the penalty of executing an external toolbrownhamer wrote:Another solution could be to have an option to use the default resolving of the /cygdrive/n pattern, and the more generic option as a last resort.
Thus:
- check if the file in 'fullname' is a valid file, if not use the value from 'file'
- check if the file in 'file' is a valid file, if not check if the /cygdrive/n pattern option is selected and the 'fullname' or 'file' starts with /cygdrive
- check if the command to resolve the path option is selected
Executing new process is slow under Windows (and it will be noticeable) - this is why the cache is needed.EddieG wrote:I guess it depends on whether the resolving with an external tool is actually noticeable when debugging
It sure is, modifying fstab during debugging I consider a no no.and even in this case, it is reasonable to require codelite restart