[petsc-users] Debugger fails because of nanosleep.c

[Jed Brown]

Thibaut Appel <t.appel17 at imperial.ac.uk> writes:

> Good afternoon,
>
> I have a "Caught signal number 11 SEGV: Segmentation Violation, probably 
> memory access out of range" error on my application code.
> After changing from 1 to 0 in /proc/sys/kernel/yama/ptrace_scope, I 
> tried to start my code with -start_in_debugger and -fp_trap but in the 
> x-terminal that pops up, I have
>
> 0x00007f06f19f69a4 in __GI___nanosleep (requested_time=0x7ffc064c15a0,
>      remaining=0x7ffc064c15a0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
> 28      ../sysdeps/unix/sysv/linux/nanosleep.c: No such file or directory.
>
> popping up. How can I solve this?

Please include backtrace output (type "bt" at the gdb prompt) when
writing.  You may just need to "continue".

> Running Ubuntu 18.04 LTS with petsc 3.9.2, my code is compiled with the 
> following flags
>
> -Wall -ffree-line-length-0 -Wno-unused-dummy-argument -g  -Og 
> -fimplicit-none -std=f2018 -pedantic -fmodule-private -fcheck=all 
> -fbacktrace -ffpe-trap=invalid,zero,overflow
>
> PETSc is configured with --with-cc=gcc-8 --with-cxx=g++-8 
> --with-fc=gfortran-8 --with-scalar-type=complex --with-precision=double 
> --with-debugging=1 --with-fortran-kernels=1 --with-x=1 --download-mpich 
> --download-fblaslapack --download-scalapack --download-metis 
> --download-parmetis --download-ptscotch --download-mumps --with-debugger=gdb
>
> My xTerm version seems to be 330.
>
> Thank you for any useful piece of information,
>
> Thibaut