<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Jose,<div class=""><br class=""></div><div class="">Even when I have PETSc --with-debugging=1 and SLEPc picks it up during configure, </div><div class="">i don’t seem to have debug symbols in resulting SLEPc lib (make stage):</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class="">warning: no debug symbols in executable (-arch x86_64)</div><div class=""><br class="webkit-block-placeholder"></div><div class="">Same when starting a debugger:</div><div class=""><div class="">warning: (x86_64) /usr/local/opt/slepc/real/lib/libslepc.3.6.dylib empty dSYM file detected, dSYM was created with an executable with no debug info.</div></div><div class=""><br class=""></div><div class="">C/Fortran flags seems to have debug flags:</div><div class=""><br class=""></div><div class=""><div class="">Using C/C++ linker: /usr/local/bin/mpicc</div><div class="">Using C/C++ flags: -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress -Wl,-commons,use_dylibs -Wl,-search_paths_first -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -O0</div><div class="">Using Fortran linker: /usr/local/bin/mpif90</div><div class="">Using Fortran flags: -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress -Wl,-commons,use_dylibs -Wl,-search_paths_first -fPIC -Wall -Wno-unused-variable -ffree-line-length-0 -Wno-unused-dummy-argument -g -O0</div></div><div class=""><br class=""></div><div class="">Any ideas?</div><div class=""><br class=""></div><div class="">
<div class="">Kind regards,</div><div class="">Denis </div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 3 Nov 2015, at 12:20, Jose E. Roman <<a href="mailto:jroman@dsic.upv.es" class="">jroman@dsic.upv.es</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I am answering the SLEPc-related questions:<br class="">- Having different number of iterations when changing the number of processes is normal.<br class="">- Yes, if you do not destroy the EPS solver, then the preconditioner would be reused.<br class=""><br class="">Regarding the segmentation fault, I have no clue. Not sure if this is related to GAMG or not. Maybe running under valgrind could provide more information.<br class=""><br class="">Jose<br class=""></div></div></blockquote></div><br class=""></div></body></html>