[petsc-users] Debugger won't start

[Karthikeyan Chockalingam - STFC UKRI]

Thank you very much that worked!

Best,
Karthik.

On 15/11/2021, 10:50, "Jose E. Roman" <jroman at dsic.upv.es> wrote:

    -start_in_debugger -debug_terminal "/path/to/xterm -e"


    > El 15 nov 2021, a las 11:06, Karthikeyan Chockalingam - STFC UKRI <karthikeyan.chockalingam at stfc.ac.uk> escribió:
    > 
    > Thank you for your response. I am trying to debug in parallel and the used the flags in the link you sent me
    > 
    > mpirun -np 2 ./ex45 -start_in_debugger -debug_terminal "screen -X -S debug screen"
    > 
    > but the problem still persists. Now, I get a different message
    > 
    > No screen session found.
    > 
    > 
    > On 15/11/2021, 09:04, "Jose E. Roman" <jroman at dsic.upv.es> wrote:
    > 
    >    If you are debugging a program with one MPI process, you can just do "-start_in_debugger noxterm". Otherwise, have a look at https://petsc.org/release/docs/manualpages/Sys/PetscSetDebugTerminal.html
    > 
    >    Jose
    > 
    > 
    >> El 15 nov 2021, a las 9:55, Karthikeyan Chockalingam - STFC UKRI <karthikeyan.chockalingam at stfc.ac.uk> escribió:
    >> 
    >> Hello,
    >> 
    >> I am running PETSc 3.16.0 on a cluster compiled in debug mode using the flag -start_in_debugger. But I getting following error message:
    >> 
    >> Unable to start debugger in xterm. No such file or directory.
    >> 
    >> I think the program is searching in the wrong path, probably under /usr/bin but xterm is located in a different path.
    >> How do I set it to the right path?
    >> 
    >> Best,
    >> Karthik.
    >> This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. 
    >> 
    > 
    >