Re: clang 3.2 RC2 miscompiles libgcc?

From: Konstantin Belousov <kostikbel_at_gmail.com>
Date: Fri, 4 Jan 2013 20:14:38 +0200
On Fri, Jan 04, 2013 at 04:49:41PM +0100, Stefan Farfeleder wrote:
> On Wed, Jan 02, 2013 at 02:59:50PM +0100, Stefan Farfeleder wrote:
> > On Sun, Dec 30, 2012 at 11:17:10PM +0100, Dimitry Andric wrote:
> > > 
> > > I have been playing with Stefan's testcase for a while now, and while I
> > > can reproduce the crashes, I am still at a loss about the cause.  It
> > > does seem to have something to do with throwing exceptions, but I am
> > > still not sure whether I am looking at a bug in boost, gcc, clang, or
> > > libgcc...
> > > 
> > > Do you happen to have a smaller testcase, by any chance?
> > 
> > Not yet, but I'll try to come up with something smaller.
> 
> Here's a minimal test case that reproduces the bug:
> 
> $ cat throw-crash.cc
> #include <stdexcept>
> 
> void f2(void) {
>     std::string s;
>     throw std::runtime_error("foo");
> }
> 
> void f1(void) {
>     f2();
> }
> 
> int main(void) {
>     try {
>         std::string s1, s2;
>         f1();
>         return 0;
>     } catch (const std::exception &) {
>         return 1;
>     }
> }
> $ g++ -O2 -finline-limit=0 throw-crash.cc 
> $ ./a.out 
> zsh: bus error (core dumped)  ./a.out

What is the backtrace ?
Compile the system libraries (ld-elf, libc, libgcc etc) with the
debugging information and obtain the backtrace once more.

Received on Fri Jan 04 2013 - 17:14:42 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:33 UTC