https://bugs.kde.org/show_bug.cgi?id=411745
Bug ID: 411745
Summary: When cross-debugging, checking executable file
extension does not make sense
Product: kdevelop
Version: 5.3.2
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: CPP Debugger
Assignee: kdevelop-bugs-n...@kde.org
Reporter: kdeb...@funkster.org
CC: niko.s...@gmail.com
Target Milestone: ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
