---
This story begun with this post. I downloaded various GCC versions from https://developer.arm.com/tools-and-sof ... /downloads, set the PATH variable, tried to compile and then start debugging with gdb; but there is no luck.
Here is the latest status:
I downloaded "5-2016-q1-update" from above link, set the custom GCC path via my config.mk and compile/run/debug my example project with:
Code: Select all
make start-debugging
If I compile the very same project under Debian 8 virtual machine, application works as expected (debugger continues execution with "n" key after hitting a breakpoint at `chThdSleep()` line.
If I compile the very same project (exactly same files) under my host OS (Debian 9), debugger stucks after the context switch.
Here are the `build/` folder contents both generated under the `.host` and the `.vm` : https://aktos.io/cloud/index.php/s/gkcRpZZn2NO2f9T
Question
Why and how come the output (the build/ folder contents) can differ while using exactly same commit of ChibiOS and GCC?
Reproduction
1. Download my example project:
Code: Select all
git clone --recursive --single-branch --branch custom-gcc https://github.com/ceremcem/chibi-examples2
2. Download custom GCC toolset: "5-2016-q1-update" from https://developer.arm.com/tools-and-sof ... /downloads
3. Extract the GCC toolset to ~/gcc folder (or point your extraction path in config.mk)
4. "make"
5. Compare your result with above "build.host.zip" and "build.vm.zip"