Open ext-mwo opened 2 years ago
where did you look for the core file? With systemd, you can easily use coredumpctl to get at it, and it's stored is a strangely-named directory in /var
. Here's another issue with the same error:
https://github.com/nvim-treesitter/nvim-treesitter/issues/2195
EVRP is a value range propagation optimization
where did you look for the core file? With systemd, you can easily use coredumpctl to get at it, and it's stored is a strangely-named directory in
/var
. Here's another issue with the same error: nvim-treesitter/nvim-treesitter#2195
I spent some time on making coredumps work and made it create them in the current directory. On ubuntu they are placed in /var/crash or some such directory.
I executed sleep 10 and killed it with some flags - got a coredump in the same directory so the coredump functionality of my OS works. :)
This is why this is so strange and why I attached the output from strace for both gcc and the child process it creates.
I found this while looking for the same error message on a project of my own with an STM32H503.
Could it be related to this GCC bug ?
I am building project for STM32U575 using default tool chain STMCubeIDE (which is arm-none-eabi-gcc-11-3-rel1
), my code is getting compile without any error. However, when I tried to compile the same using the tool chain arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-eabi
downloaded from ARM GNU Toolchain Downloads is giving the same error as mentioned in this issue.
Could anyone please help me to fix it ?
Thank you
I get a crash while building Zaphyr/TF-M.
The GCC version:
Error message:
The command line was:
The command doesn't generate a core file - I enabled core generation in the current directory.
So I attach strace output and Src.tar.gz which contains the files generated when adding "-v -save-temps" to the command line above.
process_dump.10635.txt process_dump.10636.txt Src.tar.gz