[petsc-users] Question about correctly catching fp_trap

[Balay, Satish]

On Mon, 7 Jan 2019, Sajid Ali wrote:

> @Satish Balay <balay at mcs.anl.gov> : I tried building with the patch and
> don't see any difference. Do you want me to send you the config and build
> logs to investigate further?

Hm - you should see '-g' for 'petsc+debug'. Send the logs. 

I have - in /home/balay/spack/opt/spack/linux-fedora29-x86_64/gcc-8.2.1/petsc-3.10.3-q5v3hfhsecvhf3geffeyrm5j3bm6orup/.spack/build.out
>>>>>>>>
Compilers:
  C Compiler:         /home/petsc/soft/mpich-3.3b1/bin/mpicc    -g3 
  C++ Compiler:       /home/petsc/soft/mpich-3.3b1/bin/mpic++  -g      
  Fortran Compiler:   /home/petsc/soft/mpich-3.3b1/bin/mpif90   -g  
Linkers:
  Shared linker:   /home/petsc/soft/mpich-3.3b1/bin/mpicc  -shared    -g3
  Dynamic linker:   /home/petsc/soft/mpich-3.3b1/bin/mpicc  -shared    -g3
<<<<<

Note: the patch I sent earlier fails for 'petsc~debug' - but the
attached updated patch should work for it.

> Apart from the -g flag, as I've stated above
> another bug is that petsc uses the system gdb (rhel-7) and not the gdb
> associated with the gcc that was used to build petsc.

It uses gdb from your PATH - so you can setup your PATH to use the appropriate gdb.

Satish
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: spack-petsc-debug.patch
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20190107/8d8762fb/attachment.ksh>