Hi, Mathieu Othacehe skribis: > mathieu@meije ~/tmp [env]$ gdb ./a.out /tmp/my-core-5622 > ... > BFD: warning: /tmp/my-core-5622 has a segment extending past end of file > ... > Failed to read a valid object file image from memory. I never encountered that issue, although I’ve had to look a lot at core dumps over time. :-) --8<---------------cut here---------------start------------->8--- $ gcc test.c $ ulimit -c unlimited $ ./a.out Segmentation fault (core dumped) $ gdb a.out core GNU gdb (GDB) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from a.out... (No debugging symbols found in a.out) [New LWP 23407] Core was generated by `./a.out'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000401106 in main () (gdb) bt #0 0x0000000000401106 in main () (gdb) quit --8<---------------cut here---------------end--------------->8--- Could it have to do with /proc/sys/kernel/core_pattern or with the fact that your /tmp file system was full or something? What if you try to have the core dump on another file system? Thanks, Ludo’.