Re: Solution sought to GCC 4.1.1 backtrace problem

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

To: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
Subject: Re: Solution sought to GCC 4.1.1 backtrace problem
From: Ian Lance Taylor <iant@xxxxxxxxxx>
Date: 29 Aug 2007 19:04:09 -0700
Cc: Blair Barnett <blairbarnett@xxxxxxxxxxxxx>, David Daney <ddaney@xxxxxxxxxx>, gcc-help mailing list <gcc-help@xxxxxxxxxxx>
In-reply-to: <18133.49670.549886.598644@xxxxxxxxxxxx>
References: <969965.63040.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <18133.49670.549886.598644@xxxxxxxxxxxx>
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4

Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx> writes:

> For _Unwind_Backtrace to work, all code must be compiled with
> -fexceptions.

Or -funwind-tables.

Ian

References:
- Re: Solution sought to GCC 4.1.1 backtrace problem
  - From: Blair Barnett
- Re: Solution sought to GCC 4.1.1 backtrace problem
  - From: Andrew Haley

Prev by Date: Re: Help with -march and -mcpu issues
Next by Date: Inline assembly and local variable storage
Previous by thread: Re: Solution sought to GCC 4.1.1 backtrace problem
Next by thread: Re: Solution sought to GCC 4.1.1 backtrace problem
Index(es):
- Date
- Thread

[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