Home
last modified time | relevance | path

Searched refs:debugger (Results 1 – 18 of 18) sorted by relevance

/petsc/src/sys/error/
H A Dadebug.c77 PetscErrorCode PetscSetDebugger(const char debugger[], PetscBool usedebugterminal) in PetscSetDebugger() argument
80 if (debugger) PetscCall(PetscStrncpy(PetscDebugger, debugger, sizeof(PetscDebugger))); in PetscSetDebugger()
108 …de PetscCheckDebugger_Private(const char defaultDbg[], const char string[], const char *debugger[]) in PetscCheckDebugger_Private() argument
118 if (exists) *debugger = string; in PetscCheckDebugger_Private()
119 else *debugger = defaultDbg; in PetscCheckDebugger_Private()
139 const char *debugger = NULL; in PetscSetDebuggerFromString() local
150 PetscCall(PetscCheckDebugger_Private("xdb", string, &debugger)); in PetscSetDebuggerFromString()
151 PetscCall(PetscCheckDebugger_Private("dbx", string, &debugger)); in PetscSetDebuggerFromString()
152 PetscCall(PetscCheckDebugger_Private("xldb", string, &debugger)); in PetscSetDebuggerFromString()
153 PetscCall(PetscCheckDebugger_Private("gdb", string, &debugger)); in PetscSetDebuggerFromString()
[all …]
/petsc/lib/petsc/bin/
H A Dpetscmpiexec13 debugger=0
17 debugger=1
91 if [ ${debugger} = "1" ]; then
/petsc/config/
H A Dpetsc_harness.sh44 -d ................ Launch in debugger
72 debugger=false
83 d ) debugger=true ;;
124 if $debugger; then
/petsc/doc/miscellaneous/
H A Dcodemanagement.md56 hence, using a standard debugger such as dbx, gdb, xdbx, etc. is fine.
59 debugger; this is not the same as using a parallel debugger, but in most
66 It really pays to learn how to use a debugger; you will end up writing
84 to use a debugger. In most cases using the debugger to track down
/petsc/doc/changes/
H A D212.md10 - Allow full path of debugger to be specified using
H A D2016.md110 debugger. Can be used in conjunction with the -log_info option.
H A D315.md10 - Make Terminal the default device to display the debugger on Apple
/petsc/doc/manual/
H A Dother.md240 debugger but should be avoided in source code.
406 `[-display name]` - start all processes in debugger
408 `[-display name]` - start debugger only on encountering an error
411 usual manner of starting the programming in the debugger (because then
414 By default on Linux systems the GNU debugger `gdb` is used, on macOS systems `lldb` is used
416 By default, the debugger will be started in a new
419 the debugger command `cont` should be used to continue execution of
420 the program within the debugger. Rerunning the program through the
421 debugger requires terminating the first job and restarting the
422 processor(s); the usual `run` option in the debugger will not
[all …]
H A Dabout_this_manual.md21 experience using a debugger such as `gdb` or `lldb`, it may require a
H A Dgetting_started.md153 `[-display name]` - start all (or a subset of the) processes in a debugger. See
157 `[-display name]` - start debugger only on encountering an error
H A Dprofiling.md36 running in the debugger. See `PetscLogTraceBegin()`.
/petsc/src/ksp/ksp/tutorials/output/
H A Dex2_help.out18 only when run in the debugger
20 start the debugger in new xterm
23 start all processes in the debugger
26 -debugger_ranks [n1,n2,..] Ranks to start in debugger
27 -debugger_pause [m] : delay (in seconds) to attach debugger
28 -stop_for_debugger : prints message on how to attach debugger manually
/petsc/doc/faq/
H A Dindex.md1725 ranks in the debugger using tmux.
1727 On newer macOS machines - one has to be in admin group to be able to use debugger.
1735 to get start in debugger working.
1738debugger directly, for example: `gdb ex1`. You can also use [TotalView](https://totalview.io/produ…
1742 You can use the `-start_in_debugger` option to start all processes in the debugger (each
1747 ### How can I inspect PETSc vector and matrix values when in the debugger?
1771 display objects in the debugger. Thus in theory each PETSc object, `Vec`, `Mat` etc
1779 The best way to locate floating point exceptions is to use a debugger. On supported
1780 architectures (including Linux and glibc-based systems), just run in a debugger and pass
1782 debugger will break on the line that first divides by zero or otherwise generates an
[all …]
/petsc/src/binding/petsc4py/src/petsc4py/PETSc/
H A DSys.pyx350 elif errhandler == "debugger":
/petsc/doc/install/
H A Dwindows.md254 Make sure your environment is properly configured to use the appropriate debugger for your compiler.
/petsc/doc/developers/
H A Dkernel.md119 - `PetscAbortErrorHandler()`, called with `-onerrorabort`, useful when running in the debugger;
H A Dtesting.md595 -d ................ Launch in debugger
658 DEBUG=1 Launch tests in the debugger (-d to the scripts)
/petsc/
H A Dgmakefile.test68 TESTFLAGS += -d Launch test in debugger
504 -@echo " DEBUG=1 Launch tests in the debugger (-d to the scripts)"