Navigation : Manual Input Variables - Atomic Orbitals - Calculation Modes - ClassicalParticles - DFTBPlusInterface - Execution -- Accel -- Debug --- Debug --- DebugTrapSignals --- ExperimentalFeatures --- ForceComplex --- MPIDebugHook --- ReportMemory -- IO -- Optimization -- Parallelization -- Symmetries -- Units -- FromScratch - Hamiltonian - Linear Response - Math - Maxwell - Mesh - Output - SCF - States - System - Time-Dependent - Utilities - Alphabetic Index Tutorials Developers Releases DebugTrapSignals A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X DebugTrapSignals Section Execution::Debug Type logical Default yes If true, trap signals to handle them in octopus itself and print a custom backtrace. If false, do not trap signals; then, core dumps can be produced or gdb can be used to stop at the point a signal was produced (e.g. a segmentation fault). Source information basic/messages.F90 : 174 call parse_variable(global_namespace, 'DebugTrapSignals', .true., trap_signals) Featured in testfiles functionals/06-rdmft.03-gs_grid.inp lda_u/10-intersite.02-silicon.inp maxwell/10-current-to-maxwell.01-all-forces-non-self-consistent.inp modelmb/02-qd_2e_2d.01-gs.inp modelmb/02-qd_2e_2d.02-td.inp