Hi all. I'm really sorry, i need to resend this mail again.
I need help with recent MUMPS-5.8.* releases (not in Fedora) that produces segmentation fault by running its example files. I created the RPMs (https://copr.fedorainfracloud.org/coprs/sagitter/ForTesting/build/10125628/) including the files for testing. Debugging the previous release 5.8.1, Valgrind produces something like this $ mpirun -np 2 valgrind --tool=memcheck -s ./c_example ==34094== Memcheck, a memory error detector ==34094== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==34094== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info ==34094== Command: ./c_example ==34094== ==34095== Memcheck, a memory error detector ==34095== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==34095== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info ==34095== Command: ./c_example ==34095== vex amd64->IR: unhandled instruction bytes: 0x6 0x0 0x0 0x0 0x0 0x0 0x0 0xD9 0x6 0x0 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 vex amd64->IR: unhandled instruction bytes: 0x6 0x0 0x0 0x0 0x0 0x0 0x0 0xD9 0x6 0x0 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==34094== Invalid read of size 1 ==34095== Invalid read of size 1 ==34094== at 0x4000047: ??? (in /home/sagitter/rpmbuild/BUILD/MUMPS-5.8.1-build/MUMPS_5.8.1/MUMPS-5.8.1-openmpi/examples/c_example) ==34094== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==34094== ==34094== ==34094== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==34094== Access not within mapped region at address 0x0 ==34094== at 0x4000047: ??? (in /home/sagitter/rpmbuild/BUILD/MUMPS-5.8.1-build/MUMPS_5.8.1/MUMPS-5.8.1-openmpi/examples/c_example) ==34094== If you believe this happened as a result of a stack ==34094== overflow in your program's main thread (unlikely but ==34094== possible), you can try to increase the size of the ==34094== main thread stack using the --main-stacksize= flag. ==34094== The main thread stack size used in this run was 8388608. ==34095== at 0x4000047: ??? (in /home/sagitter/rpmbuild/BUILD/MUMPS-5.8.1-build/MUMPS_5.8.1/MUMPS-5.8.1-openmpi/examples/c_example) ==34095== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==34095== ==34095== ==34095== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==34095== Access not within mapped region at address 0x0 ==34095== at 0x4000047: ??? (in /home/sagitter/rpmbuild/BUILD/MUMPS-5.8.1-build/MUMPS_5.8.1/MUMPS-5.8.1-openmpi/examples/c_example) ==34095== If you believe this happened as a result of a stack ==34095== overflow in your program's main thread (unlikely but ==34095== possible), you can try to increase the size of the ==34095== main thread stack using the --main-stacksize= flag. ==34095== The main thread stack size used in this run was 8388608. ==34094== ==34094== HEAP SUMMARY: ==34094== in use at exit: 0 bytes in 0 blocks ==34094== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==34094== ==34094== All heap blocks were freed -- no leaks are possible ==34094== ==34094== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0) ==34094== ==34094== 2 errors in context 1 of 1: ==34094== Invalid read of size 1 ==34094== at 0x4000047: ??? (in /home/sagitter/rpmbuild/BUILD/MUMPS-5.8.1-build/MUMPS_5.8.1/MUMPS-5.8.1-openmpi/examples/c_example) ==34094== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==34094== ==34094== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0) ==34095== ==34095== HEAP SUMMARY: ==34095== in use at exit: 0 bytes in 0 blocks ==34095== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==34095== ==34095== All heap blocks were freed -- no leaks are possible ==34095== ==34095== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0) ==34095== ==34095== 2 errors in context 1 of 1: ==34095== Invalid read of size 1 ==34095== at 0x4000047: ??? (in /home/sagitter/rpmbuild/BUILD/MUMPS-5.8.1-build/MUMPS_5.8.1/MUMPS-5.8.1-openmpi/examples/c_example) ==34095== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==34095== ==34095== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0) -------------------------------------------------------------------------- prterun noticed that process rank 0 with PID 34094 on node localhost exited on signal 11 (Segmentation fault). -------------------------------------------------------------------------- I tested MUMPS by modifying some compiler options as reported in INSTALL file without any positive feedback. --- Antonio Trande Fedora Project, User:Sagitter Website: antoniotrande.blog mailto: [email protected] GPG key: 0x6ea362cc4c1aeac10b3a5c5402b0e70b4933065a GPG keys server: https://pgp.mit.edu/
INSTALL
Description: Binary data
publickey - [email protected] - 0x6EA362CC.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
