http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59061
--- Comment #8 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> --- (In reply to Kostya Serebryany from comment #7) > -fno-omit-frame-pointer: that may or may not be a good idea, I don't know. I seem to need it to get good backtraces (i.e. full stack, line numbers etc.). Might be something I'm doing wrong, it is hard to figure out what the best practice is. I agree that -g incurs some overhead, but indeed, some line number information is most helpful to debug the issues flagged by sanitizer. If there are better approaches, they could indeed substitute the plain '-g'. I hardly dare to mention it, but would be nice have these symbolic stacks printed without the symbolize python script that seems needed now (and I believe is not part of gcc). I believe in this context libbacktrace has been metioned.
