Instead of linking lldb.so, which is basically an entire debugger, maybe you could just link llvm? I don't remember which library has the stack trace function in llvm, but the function I believe is called llvm::sys::printStackTrace(). This will give you a much smaller overhead than bringing in all of lldb unnecessarily.
On Mon, Jul 27, 2015 at 10:12 PM Schlottke-Lakemper, Michael < m.schlottke-lakem...@aia.rwth-aachen.de> wrote: > Hi folks, > > We are looking for a way to use lldb.so to print out a stack trace > programmatically. In our scientific simulation tool (written in C++) , we > use a custom terminate function where we are already able to print stack > traces in case of an abnormal abort, which uses some gcc-specific magic. > > My idea is to link our tool to lldb.so when compiling for debugging and to > use the library to print a stack trace programmatically, including > demangled names and correct line numbers. However, I don't really know how > to start thus I am wondering > > - has someone here done or seen something like this before? > - is there a tutorial for linking to lldb.so and making use of it through > C++? > - would this also work when compiling with other compilers than clang? > > Any help or pointers to relevant projects/documentation etc is greatly > appreciated! > > Regards, > > Michael > > -- > Michael Schlottke-Lakemper > > SimLab Highly Scalable Fluids & Solids Engineering > Jülich Aachen Research Alliance (JARA-HPC) > RWTH Aachen University > > Wüllnerstraße 5a > 52062 Aachen > Germany > > Phone: +49 (241) 80 95188 > Fax: +49 (241) 80 92257 > Mail: m.schlottke-lakem...@aia.rwth-aachen.de > Web: http://www.jara.org/jara-hpc > > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
