[LLVMbugs] [Bug 3570] New: Mac OS X: Linking to llvm modifies behaviour of abort()

[bugzilla-daemon at cs.uiuc.edu]

http://llvm.org/bugs/show_bug.cgi?id=3570

           Summary: Mac OS X: Linking to llvm modifies behaviour of abort()
           Product: libraries
           Version: trunk
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Support Libraries
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: alexei.svitkine at gmail.com
                CC: llvmbugs at cs.uiuc.edu


The following behavior applies to Mac OS X 10.5.6 with latest updates.

Consider program abort.cpp:

#include <stdlib.h>

int main(const int argc, char **argv)
{
        abort();
        return 0;
}

Compile it normally and run:

g++ crash.cpp && ./a.out 

Produces the expected crash behaviour.

Now do the same thing, while linking to llvm:

g++ crash.cpp `llvm-config --ldflags` `llvm-config --libs` && ./a.out

As you can see the abort() behaviour is modified. Before aborting, the process
hangs for about a minute. Finally, (if you have crash reporting enabled for
non-GUI processes), the crash reporter window pops up, but instead of having
the stack trace of my program as expected (and as the case before), it instead
reports that the "application ReportCrash quit unexpectedly".

Linking to llvm libraries should not have such a side-effect on the behaviour
of abort().


-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.