Re: [Buildroot] [Aarch64] libstdc++ segfault at end of execution

From: Andreas Ziegler <br015@umbiko.net>
To: Lance Fredrickson <lancethepants@gmail.com>
Cc: Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [Aarch64] libstdc++ segfault at end of execution
Date: Thu, 11 Aug 2022 10:54:56 +0000	[thread overview]
Message-ID: <4e30650d952bc4dbe44f0ffcd92810df@umbiko.net> (raw)
In-Reply-To: <mailman.8980.1660210862.92745.buildroot@buildroot.org>

Hi Lance,

> I'm having segfaulting issues with c++ on aarch64 using uclibc-ng.
> Anyone else using aarch64 with uclibc-ng?
> I submitted a bug to gcc so am linking that here for this description.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581

Some years ago, I switched from uClibc to musl on aarch64, because 
uClibc did not fully implement thread-local storage, at least not in 
combination with multi-threaded execution, on this architecture.

The C++ library uses TLS for example to store exception related 
information, which, in my case resulted in a segmentation fault whenever 
the first exception handler was invoked, because the TLS area was 
inaccessible from the current thread.

My notes show that tests in 2021 still showed this problem.

Kind regards,
Andreas

[1] https://www.etalabs.net/compare_libcs.html

> thanks,
> Lance Fredrickson

------------------------------
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot