Bug 411745

Summary: When cross-debugging, checking executable file extension does not make sense
Product: [Applications] kdevelop Reporter: Funkster <kdebugs>
Component: CPP DebuggerAssignee: kdevelop-bugs-null
Status: REPORTED ---    
Severity: normal CC: niko.sams
Priority: NOR    
Version First Reported In: 5.3.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Funkster 2019-09-09 09:15:46 UTC
SUMMARY
When compiling binaries for a cross target (e.g. bare metal ARM), .exe is not an appropriate file extension. .elf or .axf are common. However if these are used then KDevelop complains that the target is not executable, even though it would be happily accepted by the cross-GDB.


STEPS TO REPRODUCE
1. Compile for cross target, resulting in output.axf
2. Pick this file in the launch configurator, choose appropriate cross-GDB in the debug options.
3. Debug launch.

OBSERVED RESULT
KDE pops up error message:

Process Error - KDevelop
"'path/output.axf' is not an executable"

EXPECTED RESULT
No error, debugging continues.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
Workaround: configure toolchain to output .exe extension or make a copy of the output file with .exe extension, and pick that in the launch configuration. Not ideal, may cause issues with antivirus etc.
Comment 1 Funkster 2019-09-09 09:16:51 UTC
Also checked on 5.4.1, same problem.