GCC debugger stack trace displays wrong file name and line number

Question

I am trying to port a fairly large C++ project to using g++ 4.0 on Mac OS X. My project compiles without errors, but I can\'t get GDB to work properly. When I look at the stack

Answer 1

I encountered this several years ago when transitioning from the Codewarrior compilers to Xcode. I believe the way to get around this is to put the flag "-fno-inline-functions" in Other C Flags (for Dev only).

This problem was more pronounced on the PowerPC architecture for us.

What about if you remove the "-fvisibility-inlines-hidden" and "-mfix-and-continue" flags?

I've never had the "fix and continue" feature work properly for me.