Replies: 5 comments 22 replies
-
If the problem occurs with the xPack binaries and does not occur with the original Arm binaries, you are in the right place. If the problem also occurs with the Arm binaries, you should report it to Arm. FYI, the xPack binaries are compiled from exactly the same source files as the Arm binaries, with (hopefully!) the same configuration options, expecting them to behave the same (good or bad). When reporting compiler issues, in order for the compiler maintainers to reproduce the issue, you have to identify the shortest possible source file which, when compiled by hand in a terminal, exhibits the issue. |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for investigating and your advice so far.. so I have confirmed that replacing the folder at Guess that means it is an xpack issue and I shall create a bug report here? To keep things more standardised I did this testing on a Docker container created from ubuntu:22.04, confirmed the issue still existed, and that the test above solved it. |
Beta Was this translation helpful? Give feedback.
-
first draft.. will post as issue later IssueUpdated from STMicroelectronics:stm32 2.4.0 to 2.5.0 and now I can't compile my project with It seems the issue is the change in bundled version of xpack-arm-none-eabi-gcc from 10.3.1-2.3 to 12.2.1-1.2 Steps to reproduceDockerfile
on you local host build the docker container:
now connect to container, create a empty test project:
now compile:
See we get Segmentation fault. Steps to test the original arm binariesDownload, extract and replace the xpack-arm-none-eabi-gcc
and compile again:
Working! Confirms the issue it with the xpack binaries bundled with STM32duino core. |
Beta Was this translation helpful? Give feedback.
-
Upgrading the server now... Beowulf kernel in use is: 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux |
Beta Was this translation helpful? Give feedback.
-
I installed a VM with Beowulf and did some further tests. I confirm that cc1plus crashes, even when started without any arguments. cc1 runs fine, so the toolchain can compile C programs. Since the cc1plus binary has no debug info, I can not run a debug session. My current theory is that the kernel or one of the system libraries has a small difference compared to regular systems. Since the xPack toolchain is by design intended to be standalone, it includes most of the required libraries, including libstdc++, in the package. This later is required since the toolchain is compiled with a newer GCC than available in the Ubuntu 18 where the build is performed, and the resulting binary needs the newer library. The Arm toolchain expects that all libraries are available in the system, and so its dependencies are in sync with the kernel or whatever small difference exists. Given that after upgrading the server to a newer kernel the problem no longer occurs, I'll probably not investigate further, and revisit it only in case other similar issues are reported. |
Beta Was this translation helpful? Give feedback.
-
I'm building a project using arduino-cli and STM32 core. After a recent update I get segfault. I have been directed here. Issue tracker was very insistent I post to forums first if unsure so here I am...
Full details can be found here: stm32duino/Arduino_Core_STM32#2008
Am I in the fight place? Should I post this as an issue on this repo?
Beta Was this translation helpful? Give feedback.
All reactions