public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lancethepants at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106581] [Aarch64] libstdc++ segfault at end of execution Date: Wed, 10 Aug 2022 22:03:27 +0000 [thread overview] Message-ID: <bug-106581-4-ansNOxzVdQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106581-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581 --- Comment #2 from Lance Fredrickson <lancethepants at gmail dot com> --- Here is the disassemble (gdb) disassemble Dump of assembler code for function _ZSt18uncaught_exceptionv: 0x0000007fb7eae2a8 <+0>: stp x29, x30, [sp, #-16]! 0x0000007fb7eae2ac <+4>: mov x29, sp 0x0000007fb7eae2b0 <+8>: bl 0x7fb7ea8dd0 <__cxa_get_globals@plt> => 0x0000007fb7eae2b4 <+12>: ldr w0, [x0, #8] 0x0000007fb7eae2b8 <+16>: cmp w0, #0x0 0x0000007fb7eae2bc <+20>: cset w0, ne // ne = any 0x0000007fb7eae2c0 <+24>: ldp x29, x30, [sp], #16 0x0000007fb7eae2c4 <+28>: ret End of assembler dump.
next prev parent reply other threads:[~2022-08-10 22:03 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-10 21:18 [Bug libstdc++/106581] New: " lancethepants at gmail dot com 2022-08-10 21:47 ` [Bug libstdc++/106581] " pinskia at gcc dot gnu.org 2022-08-10 22:03 ` lancethepants at gmail dot com [this message] 2022-08-10 22:05 ` pinskia at gcc dot gnu.org 2022-08-10 22:11 ` lancethepants at gmail dot com 2022-08-10 22:14 ` pinskia at gcc dot gnu.org 2022-08-10 22:15 ` lancethepants at gmail dot com 2022-08-10 22:17 ` pinskia at gcc dot gnu.org 2022-08-10 22:27 ` lancethepants at gmail dot com 2022-08-10 22:33 ` pinskia at gcc dot gnu.org 2022-08-10 22:35 ` lancethepants at gmail dot com 2022-08-10 22:41 ` [Bug target/106581] " pinskia at gcc dot gnu.org 2022-08-10 22:49 ` lancethepants at gmail dot com 2022-11-30 21:53 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-106581-4-ansNOxzVdQ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).