This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH RFA: Print backtrace on ICE

From: Ian Lance Taylor <iant at google dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Markus Trippelsdorf <markus at trippelsdorf dot de>, gcc-patches at gcc dot gnu dot org
Date: Tue, 18 Sep 2012 09:25:45 -0700
Subject: Re: PATCH RFA: Print backtrace on ICE
References: <mcrfw6gpo0s.fsf@google.com> <CAFiYyc2HvWZ9-dLrp6JjGwfPSp+rDbnX_1nfi_bP36fpN=u9sg@mail.gmail.com> <CAKOQZ8y-XnnpnAGRbCorsTOYMc+UE2YOdkOqTT6s3PTKu+iaGA@mail.gmail.com> <20120918144023.GA262@x4> <CAFiYyc1hGenJSF6mZkPpVQZ4OWp9CD3xwUtDjBsfX=+n7twSMA@mail.gmail.com>

On Tue, Sep 18, 2012 at 7:55 AM, Richard Guenther
<richard.guenther@gmail.com> wrote:
>
> Indeed - we ship binaries with stripped debug info, usually not installed.
> libbacktrace will only produce useless garbage then.  So I want a way
> to disable it (at least by default) at configure time.

The library won't print useless garbage.  That would be pointless.  It
simply won't print anything at all.

I can add a configure option to not dump backtraces if you really want
it.  I only care that the default is to print them.

Ian

References:
- PATCH RFA: Print backtrace on ICE
  - From: Ian Lance Taylor
- Re: PATCH RFA: Print backtrace on ICE
  - From: Richard Guenther
- Re: PATCH RFA: Print backtrace on ICE
  - From: Ian Lance Taylor
- Re: PATCH RFA: Print backtrace on ICE
  - From: Markus Trippelsdorf
- Re: PATCH RFA: Print backtrace on ICE
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]