This is the mail archive of the
mailing list for the GCC project.
Re: Using libbacktrace in libgfortran: some questions
- From: FX <fxcoudert at gmail dot com>
- To: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- Cc: Ian Lance Taylor <ian at airs dot com>, GCC Development <gcc at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>
- Date: Thu, 13 Aug 2015 16:14:12 +0200
- Subject: Re: Using libbacktrace in libgfortran: some questions
- Authentication-results: sourceware.org; auth=none
- References: <8880A586-94DE-4745-B2BD-E07582E0F1DD at gmail dot com> <m3r3n7l2vb dot fsf at pepe dot airs dot com> <CAO9iq9F8gifRf9NE1cfb6TdssWvPra84udNtv72rgcrTKTfUJw at mail dot gmail dot com>
> You might also take a look at the patch posted to PR 54572 which was my attempt to use libbacktrace a few years ago. While I got symbolic backtraces working somewhat, unfortunately I never got it to work completely since it crashed somewhere in libbacktrace in some cases, but maybe whatever bugs caused that have been fixed in the meantimeâ
I definitely did start from your patch at PR 54572!
libbacktrace definitely has improved, and now supports pecoff targets (i.e. Windows, I think). If we can get rid of the last few hurdles, then it will be a perfect solution for libgfortran, given it is already used in the compiler itself (and thus well-maintained).
Obviously, the major target for which support is missing is Darwin (Mach-O object files). I have looked at implementing it, but it is well beyond my simple understanding of object filesâ inner working :(