On 7/5/26 12:11, Victor Eijkhout wrote:
*** Caution: EXTERNAL Sender ***
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?
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.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/dealii/8668b7ab-33e1-4b2c-9684-425c766f1bb3%40colostate.edu.
