public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Debug Mode ENH 3/4: Add backtrace
Date: Wed, 09 May 2018 09:05:00 -0000	[thread overview]
Message-ID: <20180509090506.GR20930@redhat.com> (raw)
In-Reply-To: <CAKOQZ8ys+hhF3JuB9RkdrJZef+Z+VpiSxMbZ4yqKE5YH9Ad6GA@mail.gmail.com>

On 08/05/18 16:51 -0700, Ian Lance Taylor via libstdc++ wrote:
>On Tue, May 8, 2018 at 12:54 PM, François Dumont <frs.dumont@gmail.com> wrote:
>>
>> I'll go with this version for now but I'll look into libbacktrace.
>>
>> It will be perhaps the occasion to play with autoconf & al tools to find out
>> if I can use libbacktrace.
>
>In GCC libgo and libgfortran already use libbacktrace, so there are
>good examples to copy.

And if there are any concerns about adding an extra dependency to
libstdcOO.so or increasing the size of libstdc++.a we could
conditionally use libbacktrace for the unoptimized versions of libstdc++
installed into $libdir/debug/ when --enable-libstdcxx-debug is used
(which is orthogonal to the Debug Mode).

That would allow getting nicer backtraces by linking to the debug
libs, without adding an unconditional dependency that is only used by
code compiled with _GLIBCXX_DEBUG.


      reply	other threads:[~2018-05-09  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 20:20 François Dumont
2018-05-08 15:27 ` Jonathan Wakely
2018-05-08 19:54   ` François Dumont
2018-05-08 23:51     ` Ian Lance Taylor via libstdc++
2018-05-09  9:05       ` Jonathan Wakely [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180509090506.GR20930@redhat.com \
    --to=jwakely@redhat.com \
    --cc=frs.dumont@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).