Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    In general it is impossible to know what is behind pointers at compile time. Unless the particular usage is trivial, in which case it should be replaced by direct calls anyway. Commented Sep 21, 2024 at 6:36
  • You need to analyse the systematics behind this, there is no easy way around this. Commented Sep 21, 2024 at 7:30
  • @ close voters, though we do not provide help for debugging specific code, conceptual debugging questions do clearly belong to software engineering. This question is quite broad, of course, and might be closed with "needs more focus", but not as "off topic" Commented Sep 21, 2024 at 7:34
  • You have to run the program then generate a backtrace. Especially in C, there are all sorts of ways to "smuggle" pointers around untraceably, so producing a fully static callgraph is impossible. Commented Sep 23, 2024 at 8:57