now impossible to debug code that uses PETSc shared libraries?
Barry Smith
bsmith at mcs.anl.gov
Thu May 1 08:57:32 CDT 2008
It seems to now be impossible to debug in code that uses PETSc
shared libraries
fi; \
if [ "$$flag" != "" ]; then \
echo "building $$LIBNAME.${SL_LINKER_SUFFIX}"; \
${RM} -f ${INSTALL_LIB_DIR}/tmp-petsc-shlib/*; \
cd ${INSTALL_LIB_DIR}/tmp-petsc-shlib; \
${AR} x ${INSTALL_LIB_DIR}/$$LIBNAME.${AR_LIB_SUFFIX}; \
cd $$cwd;\
${OMAKE} LIBNAME=$$LIBNAME SHARED_LIBRARY_TMPDIR=$
{INSTALL_LIB_DIR}/tmp-petsc-shlib shared_arch; \
fi; \
fi; \
done; \
${RM} -rf ${INSTALL_LIB_DIR}/tmp-petsc-shlib; \
fi
In the debugger, of course, one gets
warning: Could not find object file "/Users/bsmith/Src/petsc-dev-for-
fixes/shit/lib/tmp-petsc-shlib/bvec2.o" - no debug information
available for "bvec2.c".
since the .o files are removed the debugger cannot find any debug
information.
Is this intentional? Seems pretty terrible to give up debugging just
to use shared libraries.
Barry
More information about the petsc-dev
mailing list