Stack trace

[Victor Eijkhout]

My code was definitely compiled with "-g" but:

An error occurred in line <509> of file </scratch/00434/eijkhout/htmri25/Sources/dealii/dealii-9.7.1/source/lac/trilinos_solver.cc> in function
    void dealii::TrilinosWrappers::SolverBase::do_solve(const Preconditioner &) [Preconditioner = dealii::TrilinosWrappers::PreconditionBase]
Additional information:
    AztecOO::Iterate error code -3: loss of precision

Stacktrace:
-----------
#0  /scratch/00434/eijkhout/htmri25/Binaries/dealii-9.7.1/lib/libdeal_II.so.9.7.1: void dealii::TrilinosWrappers::SolverBase::do_solve<dealii::TrilinosWrappers::PreconditionBase>(dealii::TrilinosWrappers::PreconditionBase const&)
#1  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x4d247d]
#2  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x4cfe36]
#3  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x4cc3bb]
#4  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x4b64bd]
#5  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x475950]
#6  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x471f50]
#7  /usr/lib64/libc.so.6:
#8  /usr/lib64/libc.so.6: __libc_start_main
#9  /work2/00434/eijkhout/htmr_sandbox/installation-step32v2-intel25.3/step32v2: ) [0x470745]

--------------------------------------------------------

How do I get a stacktrace of the D2 calls?

Victor.

[Daniel Arndt]

Victor, just use a debugger (gdb, lldb, gdb-oneapi) like you would for
every other code as well.

Best,
Daniel

> --
> The deal.II project is located at http://www.dealii.org/
> For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en
> ---
> You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dealii+un...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/dealii/6e2bdc32-3d7e-450a-b477-48bc70c7e428n%40googlegroups.com.

[Victor Eijkhout]

1. Normally I would use a debugger but our systems are awaiting a big OS update because of the ptrace security problem

https://www.sentinelone.com/vulnerability-database/cve-2026-45253/

2. I don't quite understand how you generate that stack trace, but am I something missing that its output is so cryptic?

[Wolfgang Bangerth]

On 7/5/26 12:11, Victor Eijkhout wrote:
> *** Caution: EXTERNAL Sender ***

We create the stack trace in this code:
https://github.com/dealii/dealii/blob/master/source/base/exceptions.cc#L242-L339
In other words, we use the libc's backtrace()/backtrace_symbols() function
calls, and then if available a demangler to decode the information into actual
function names.

I don't know why that doesn't yield anything more useful on your system. It's
possible that using the Intel compiler, backtrace_symbols() doesn't give
anything useful. But I really can't say without trying this on a system with
that compiler.

Best
W.