[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread lancethepants at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #10 from Lance Fredrickson --- (gdb) disassemble 0x7fb7eae3b8 Dump of assembler code for function (anonymous namespace)::get_global(): 0x007fb7eae3b8 <+0>: stp x29, x30, [sp, #-16]! 0x007fb7eae3bc <+4>: mov

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #9 from Andrew Pinski --- disassemble 0x7fb7eae3b8 Which was: 0x007fb7eae3fc <+8>: bl 0x7fb7eae3b8 <(anonymous namespace)::get_global()> I am still trying to figure out how the TLS address was formed here.

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread lancethepants at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #8 from Lance Fredrickson --- Here is 'info proc mappings' (gdb) info proc mappings process 16896 Mapped address spaces: Start Addr End Addr Size Offset objfile 0x555000 0x556000

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #7 from Andrew Pinski --- (In reply to Lance Fredrickson from comment #6) > info mem gives > > (gdb) info mem > Using memory regions provided by the target. > There are no memory regions defined. Sorry, I mean "info proc mappings"

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread lancethepants at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #6 from Lance Fredrickson --- info mem gives (gdb) info mem Using memory regions provided by the target. There are no memory regions defined.

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #5 from Andrew Pinski --- uclibc must have some ordering issue when it comes to atexit and shared libraries and TLS. Can you also do: "info mem"

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread lancethepants at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #4 from Lance Fredrickson --- Here you go. (gdb) info registers x0 0xff6fea06f01097094268656 x1 0x7fb7ffa6c0548547831488 x2 0x0 0 x3 0x0

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #3 from Andrew Pinski --- (In reply to Lance Fredrickson from comment #2) > Here is the disassemble > > (gdb) disassemble > Dump of assembler code for function _ZSt18uncaught_exceptionv: >0x007fb7eae2a8 <+0>: stp

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread lancethepants at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #2 from Lance Fredrickson --- Here is the disassemble (gdb) disassemble Dump of assembler code for function _ZSt18uncaught_exceptionv: 0x007fb7eae2a8 <+0>: stp x29, x30, [sp, #-16]! 0x007fb7eae2ac <+4>:

[Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution

2022-08-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|