From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3F4553858D20; Thu, 14 Sep 2023 00:55:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3F4553858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1694652937; bh=fj0An2HL5V8PAUh53Elb6MKSzxZ/iYVUIo5ZFFeUNpo=; h=From:To:Subject:Date:From; b=h8p0eY2bsCXa6eMDrzxBSM2vIMxjlcsyT32GpzLfR8Y7wO+I8IICu3XbsrwRGPqsn QhPqmFXY4vNGpfHsprhSZXCdkTfAf9ZuHTcEoa/0ub4nHLzw1iPMuP4UsBGr9y9KEE +kaxUKUKhYwYsZjSVt5rDI9nhJnNuVZWP4H5+2/w= From: "dbrumley at forallsecure dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/30847] New: gdbtypes.c:3355: internal-error causes gdb to abort when setting breakpoint Date: Thu, 14 Sep 2023 00:55:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dbrumley at forallsecure dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30847 Bug ID: 30847 Summary: gdbtypes.c:3355: internal-error causes gdb to abort when setting breakpoint Product: gdb Version: 13.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dbrumley at forallsecure dot com Target Milestone: --- Created attachment 15110 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D15110&action=3Ded= it core file and program triggering problem. Setting any breakpoint, even without running the program, seems to cause GD= B to crash. GDB tells me it's a bug and to report it, so here I am :) I didn't see any signs it was a duplicate, but please be kind if I'm missing something obvio= us. Tested on GDB version: ``` root@90f6f1dea939:/# gdb --version GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. ``` GDB session. ``` root@90f6f1dea939:/# gdb /mnt/extract75-patched=20 GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /mnt/extract75-patched... (gdb) break main /build/gdb-IRllI9/gdb-13.1/gdb/gdbtypes.c:3570: internal-error: init_complex_type: Assertion `can_create_complex_type (target_type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0xaaaaab2c9c3b ??? 0xaaaaab60bf9b ??? 0xaaaaab60c183 ??? 0xaaaaab7b2913 ??? 0xaaaaab3f1a5f ??? 0xaaaaab56a89b ??? 0xaaaaab56dcef ??? 0xaaaaab34491f ??? 0xaaaaab34564b ??? 0xaaaaab4cfdf7 ??? 0xaaaaab3453e3 ??? 0xaaaaab4cfdf7 ??? 0xaaaaab3453e3 ??? 0xaaaaab3442db ??? 0xaaaaab4cd687 ??? 0xaaaaab4d0bdf ??? 0xaaaaab57fa23 ??? 0xaaaaab596ad3 ??? 0xaaaaab596d67 ??? 0xaaaaab5561db ??? 0xaaaaab591f9b ??? 0xaaaaab596547 ??? 0xaaaaab59848b ??? 0xaaaaab5987bb ??? 0xaaaaab33528f ??? 0xaaaaab335bdf ??? 0xaaaaab33520b ??? 0xaaaaab43b44f ??? 0xaaaaab43dd03 ??? 0xaaaaab43e607 ??? 0xaaaaab43e92f ??? 0xaaaaab2c0f1b ??? 0xaaaaab2c184b ??? 0xaaaaab2f86f3 ??? 0xaaaaab5cfefb ??? 0xaaaaab3c3723 ??? 0xaaaaab3c4bcb ??? 0xaaaaab3c40b3 ??? 0xffffbd9690bb ??? 0xaaaaab3c41f3 ??? 0xaaaaab3c4377 ??? 0xaaaaab3c35f7 ??? 0xaaaaab7b2da3 ??? 0xaaaaab7b384b ??? 0xaaaaab46adaf ??? 0xaaaaab46c7d7 ??? 0xaaaaab211183 ??? 0xffffbc76777f __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0xffffbc767857 __libc_start_main_impl ../csu/libc-start.c:360 0xaaaaab2173af ??? 0xffffffffffffffff ??? --------------------- /build/gdb-IRllI9/gdb-13.1/gdb/gdbtypes.c:3570: internal-error: init_complex_type: Assertion `can_create_complex_type (target_type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: . /build/gdb-IRllI9/gdb-13.1/gdb/gdbtypes.c:3570: internal-error: init_complex_type: Assertion `can_create_complex_type (target_type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) ``` --=20 You are receiving this mail because: You are on the CC list for the bug.=