Skip to main content
Associate
April 24, 2024
Question

STM32CubeIDE crashes - Problem: EXC_BAD_ACCESS (SIGABRT)

  • April 24, 2024
  • 3 replies
  • 1362 views

I'm using MacOS and I'm trying to build the default code on `main.c` on the STM32CubeIDE which is below:

#include <stdint.h>

#if !defined(__SOFT_FP__) && defined(__ARM_FP)
#warning "FPU is not initialized, but the project is compiling for an FPU. Please initialize the FPU before use."
#endif

int main(void)
{
/* Loop forever */
for(;;);
}

But I'm getting the following error:

`22:10:25 **** Incremental Build of configuration Debug for project 001HelloWorld ****
make -j7 all
"make -j7 all" terminated with exit code -1. Build might be incomplete.`


Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0x18:
-->
__TEXT 0000000004e25000-0000000004e29000 [ 16K] r-x/r-x SM=COW /Applications/STM32CubeIDE.app/Contents/MacOS/STM32CubeIDE

Application Specific Information:
crashed on child side of fork pre-exec


Apparently it's trying to access an invalid memory location? Any help is greatly appreciated in fixing it. Here's a bigger screenshot if it helps: https://i.sstatic.net/FpallAVo.png

This topic has been closed for replies.

3 replies

Rim LANDOLSI
ST Employee
May 7, 2024

Hello @tadm123 and welcome to the community,

 

Could you provide the used STM32CubeIDE version and macOS?

Thanks,

Rim

tadm123Author
Associate
May 7, 2024

MacOS Catalina version 10.15.7 (19H2026)

STM32CubeIDE version 1.15.0

Rim LANDOLSI
ST Employee
May 7, 2024

Hello @tadm123 ,

According to the release note of STM32CubeIDE 1.15.0, the required  macOs systems are Sonoma and Ventura as shown in the screenshot

RimLANDOLSI_0-1715088084437.png

Thanks,

Rim