public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/106977] New: [13 regression] d21 dies with SIGBUS on 32-bit Darwin Date: Tue, 20 Sep 2022 14:06:21 +0000 [thread overview] Message-ID: <bug-106977-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106977 Bug ID: 106977 Summary: [13 regression] d21 dies with SIGBUS on 32-bit Darwin Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ro at gcc dot gnu.org CC: iains at gcc dot gnu.org Target Milestone: --- Target: i386-apple-darwin11.4.2 Between 20220610 (5940b4e59f8e198dbf7e8b733561ef72a9ba2cbc) and 20220624 (3b8794302b52a819ca3ea78238e9b5025d1c56dd), 32-bit bootstrap started to fail on 32-bit Darwin (Mac OS X 10.7): when configuring the stage 2 libphobos, d21 dies with $ cat conftest.d module object; extern(C) int main() { return 0; } $ d21 conftest.d -I <path to>/libphobos/libdruntime -o conftest.s conftest.d:3:15: internal compiler error: Bus error: 10 3 | extern(C) int main() { | ^ I had a hard time getting more information out of this crash: * With gdb 9.1 I get Program received signal SIGBUS, Bus error. 0x00055398 in _ZN11Declaration7visibleEv (this=0x7) (gdb) bt #0 0x00055398 in _ZN11Declaration7visibleEv (this=warning: (Internal error: pc 0x7 in read in psymtab, but not in symtab.) 0x7) #1 0x001ed871 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) which is Declaration::visible() * With /usr/bin/gdb: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x0000004b _ZN11Declaration7visibleEv (this=0x7) at /vol/gcc/src/hg/master/darwin/gcc/d/dmd/declaration.d:547 547 return visibility; (gdb) bt #0 _ZN11Declaration7visibleEv (this=0x7) at /vol/gcc/src/hg/master/darwin/gcc/d/dmd/declaration.d:547 #1 0x001ed871 in get_symbol_decl () at parsetimevisitor.d:26 * With /usr/bin/lldb: Process 133 stopped * thread #1: tid = 0x1f03, 0x00055398 d21`Declaration::visible(this=0x00000007) + 8 at declaration.d:547, stop reason = EXC_BAD_ACCESS (code=2, address=0x4b) frame #0: 0x00055398 d21`Declaration::visible(this=0x00000007) + 8 at declaration.d:547 544 545 override final Visibility visible() pure nothrow @nogc @safe 546 { -> 547 return visibility; 548 } 549 550 override final inout(Declaration) isDeclaration() inout pure nothrow @nogc @safe (lldb) bt * thread #1: tid = 0x1f03, 0x00055398 d21`Declaration::visible(this=0x00000007) + 8 at declaration.d:547, stop reason = EXC_BAD_ACCESS (code=2, address=0x4b) frame #0: 0x00055398 d21`Declaration::visible(this=0x00000007) + 8 at declaration.d:547 frame #1: 0x001ed871 d21`get_symbol_decl(Declaration*) (.part.0) + 833 I haven't tried reghunting yet.
next reply other threads:[~2022-09-20 14:06 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 14:06 ro at gcc dot gnu.org [this message] 2022-09-21 7:48 ` [Bug d/106977] " rguenth at gcc dot gnu.org 2022-11-07 14:37 ` ibuclaw at gdcproject dot org 2022-11-07 14:49 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-11-07 15:34 ` ibuclaw at gdcproject dot org 2022-11-07 15:43 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-02-22 23:58 ` iains at gcc dot gnu.org 2023-02-23 1:20 ` ibuclaw at gcc dot gnu.org 2023-02-23 7:38 ` iains at gcc dot gnu.org 2023-02-23 10:21 ` iains at gcc dot gnu.org 2023-02-23 10:43 ` ibuclaw at gcc dot gnu.org 2023-02-23 10:50 ` ibuclaw at gcc dot gnu.org 2023-02-23 10:51 ` iains at gcc dot gnu.org 2023-02-23 22:49 ` ibuclaw at gcc dot gnu.org 2023-02-23 23:11 ` ibuclaw at gcc dot gnu.org 2023-02-23 23:29 ` iains at gcc dot gnu.org 2023-02-23 23:33 ` pinskia at gcc dot gnu.org 2023-02-23 23:34 ` iains at gcc dot gnu.org 2023-02-23 23:36 ` iains at gcc dot gnu.org 2023-02-23 23:55 ` pinskia at gcc dot gnu.org 2023-02-24 0:00 ` pinskia at gcc dot gnu.org 2023-02-24 1:13 ` ibuclaw at gcc dot gnu.org 2023-02-24 2:03 ` ibuclaw at gcc dot gnu.org 2023-02-24 2:12 ` ibuclaw at gcc dot gnu.org 2023-02-24 7:52 ` iains at gcc dot gnu.org 2023-02-24 8:20 ` ibuclaw at gcc dot gnu.org 2023-02-24 8:46 ` iains at gcc dot gnu.org 2023-02-24 11:39 ` ibuclaw at gcc dot gnu.org 2023-02-24 17:48 ` iains at gcc dot gnu.org 2023-02-24 18:14 ` iains at gcc dot gnu.org 2023-02-24 18:39 ` ibuclaw at gcc dot gnu.org 2023-02-24 20:07 ` iains at gcc dot gnu.org 2023-04-26 6:56 ` [Bug d/106977] [13/14 " rguenth at gcc dot gnu.org 2023-06-28 18:19 ` cvs-commit at gcc dot gnu.org 2023-06-28 18:52 ` cvs-commit at gcc dot gnu.org 2023-06-28 18:57 ` ibuclaw at gcc dot gnu.org 2023-06-29 7:52 ` iains 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-106977-4@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).