On 10/11/22 23:19, 'yy.wayne' via deal.II User Group wrote:
**
Specifically, when a Trilinos::SolverDirect object calls solve(), the line
solver_control.check(0,0)
is not executed.
I've debuged with both QT and gdb but error information is similiar, both only
returns a segmentation fault
Wayne:
I know nothing about the code in question, but have this advice:
The way to debug segmentation faults is to run the program in a debugger and
do two things:
* Take a look at the backtrace (=call stack) to know where you are when the
segfault happens
* In the debugger, go to the function where the problem happens and inspect
the local variables. A segfault means that you are accessing memory you are
not allowed to look at, and it is useful to know what variable it is you are
accessing. Typically, this is either an invalid array access, or derefencing
NULL or uninitialized pointers. You can often infer what happened if you know
what variable causes the invalid access.
I believe that I show something like this process in one of my video lectures,
but there are also certainly many other videos on youtube that show this
general procedure.
Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: bange...@colostate.edu
www: http://www.math.colostate.edu/~bangerth/
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dealii/fc2ed2b1-c8b6-62ff-8508-cbcfc8985f7a%40colostate.edu.
