* [Buildroot] [Aarch64] libstdc++ segfault at end of execution
@ 2022-08-10 21:30 Lance Fredrickson
0 siblings, 0 replies; 3+ messages in thread
From: Lance Fredrickson @ 2022-08-10 21:30 UTC (permalink / raw)
To: buildroot
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
thanks,
Lance Fredrickson
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Buildroot] [Aarch64] libstdc++ segfault at end of execution
[not found] <mailman.8980.1660210862.92745.buildroot@buildroot.org>
@ 2022-08-11 10:54 ` Andreas Ziegler
0 siblings, 0 replies; 3+ messages in thread
From: Andreas Ziegler @ 2022-08-11 10:54 UTC (permalink / raw)
To: Lance Fredrickson; +Cc: Buildroot
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Buildroot] [Aarch64] libstdc++ segfault at end of execution
@ 2022-09-02 14:21 Alex Roberts
0 siblings, 0 replies; 3+ messages in thread
From: Alex Roberts @ 2022-09-02 14:21 UTC (permalink / raw)
To: buildroot@buildroot.org
[-- Attachment #1.1: Type: text/plain, Size: 725 bytes --]
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
I have been struggling to understand why I kept getting segfaults with a simple helloworld test until I found your bugzilla link. I recently created a stackoverflow post after a couple months or so of web searching and frustration.
https://stackoverflow.com/questions/73393107/segfault-when-writing-to-cerr-iostream-uclibc-ng-unhandled-exception
Linking against -static-libstdc++ worked as a work-around.
Buildroot 2022.05-rc2
GCC 11.3.0
uClibc 1.0.41
[-- Attachment #1.2: Type: text/html, Size: 4005 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-09-02 14:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.8980.1660210862.92745.buildroot@buildroot.org>
2022-08-11 10:54 ` [Buildroot] [Aarch64] libstdc++ segfault at end of execution Andreas Ziegler
2022-09-02 14:21 Alex Roberts
-- strict thread matches above, loose matches on Subject: below --
2022-08-10 21:30 Lance Fredrickson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.