http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59061
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Kostya Serebryany from comment #9) > We have work-in-progress to make the symbolizer in-process as opposed to > the current one that is out-of-process (uses pipes): > https://code.google.com/p/address-sanitizer/source/browse/ > #svn%2Ftrunk%2Finternal_symbolizer Why don't you use libbacktrace for that? It is not GPL, so Apple and other GPL haters can't complain, maintained by Google, and IMHO it is far better to just use existing code base for that rather than writing yet another DWARF parser. Especially if you are writing it as part of llvm, it will unlikely handle all the DWARF GNU extensions needed to symbolize GCC code. Sure, there is work to be done on libbacktrace to handle some still unhandled extensions (e.g. DWZ produced extensions), but if you use libbacktrace, that can be done just in one spot, otherwise it will need to be written two times.
