How to track the call stack of gcc

[Gwen Fu]

Dear gcc community:
I am trying to clear out  bug'119222'.It is a bug related to C++
floating-point operations where the divisor is o without warning (such as
"return 1/static_cast＜double＞0；").

Now I am managing to figure out which part of the project is about Warning
andFloating point operation.
I ran gdb and valgrind.It is feasible but a little complicated. Is there
any other method? If not, I will try to get used to it!
Best regards!