Skip to contentSkip to conversation

libstdc++ segfault at end of execution

Buildroot Andreas Ziegler 1 participant 1 message Aug 11, 2022 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi Lance,

Quoted 4 lines

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

Quoted 2 lines

thanks,
Lance Fredrickson

------------------------------
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot