Re: How to track the call stack of gcc (libbacktrace)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2025-03-14 at 17:48 +0000, Saifi Khan wrote:
> On Fri, 14 Mar 2025, Basile Starynkevitch wrote:
> 
> > 
> > The GCC compiler is containing Ian Lance Taylor's libbacktrace.
> > a possibility is to use that library to print your call stack from inside
> > your
> > C++ code inside GCC.
> > 
> 
> When i pass the option `--enable-languages=c,c++` to the `configure` script,
> it appears to me that libbacktrace is not built.
> 
> What option do I pass in order to build this library ?

The actual ELF executable (on Linux at least) using libbactrace are those
started by /usr/bin/gcc (which is only a wrapper; that program don't use
libbacktrace directly but starts other executable like cc1 and cc1plus). The
cc1plus executable is using libbacktrace.

The RefPreSys inference engine is also using libbacktrace. See code mentioned in
my signature (it is C++ and GPL licensed)

Regards

-- 
Basile STARYNKEVITCH                            <basile@xxxxxxxxxxxxxxxxx>
8 rue de la Faïencerie                       http://starynkevitch.net/Basile/  
92340 Bourg-la-Reine                         https://github.com/bstarynk
France                                https://github.com/RefPerSys/RefPerSys




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux