I tried to trace evince-3.28.4 execution using GDB. There is a callq instruction at some point in libdl, which is shown below (i.e., at _dl_lookup_symbol_x+840): When the execution reaches here, the backtrace is as follows: But when I enter ni (to jump to the next assembly instruction), it turns into this: As can be seen, after a simple call and
Tag: backtrace
Debugging segmentation fault with backtrace in cpp
In my code (written in cpp) I am getting a segmentation fault with following backtrace: So is there a way to debug this and get on which line segfault occurs? (I could not find any posts like this here, if it’s duplicate I will delete this). The code itself is pretty big so typing it here would not be correct
What is the meaning of question marks ‘?’ in Linux kernel panic call traces?
The Call Trace contains entries like that: What is the meaning of the ‘?’ mark before AnotherFunctionName? Answer ‘?’ means that the information about this stack entry is probably not reliable. The stack output mechanism (see the implementation of dump_trace() function) was unable to prove that the address it has found is a valid return address in the call stack.