From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 6EFA0386FC11; Mon, 19 Apr 2021 00:56:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6EFA0386FC11
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27743] Internal error psymtab.c
Date: Mon, 19 Apr 2021 00:56:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 10.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
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: 
Message-ID: <bug-27743-4717-Ef1Vo1iLs1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27743-4717@http.sourceware.org/bugzilla/>
References: <bug-27743-4717@http.sourceware.org/bugzilla/>
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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2021 00:56:13 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D27743

--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to Ethan Zhang from comment #6)
> Currently it seems I can only reproduce it within "CLion" the IDE I'm usi=
ng.

In CLion, there should be a way to get the "MI traces" or something like th=
at,
the log of the communication between CLion and GDB.  I've never used CLion,=
 so
I can't really help you there.  But if you can get that, it would be helpfu=
l to
reproduce the problem.  It will allow replaying the same steps, but without
CLion.

>=20
> The internal failure happens when I compile the source file using
> arm-none-eabi-gcc 9 and debug it with GDB 10 connected to openOCD. Every
> time I attempt to set a break point using the IDE triggers the internal G=
DB
> failure.
>=20
> With the exact same set up, directly setting a break point from a GDB
> terminal does not cause the failure. Even when debugging within the IDE,
> setting a break point from its own GDB terminal doesn't cause the internal
> failure.
>=20
> I'm not sure where to go from here as I don't know what's different betwe=
en
> me setting a break point from command line and the IDE setting a break po=
int.

Since the bug happens while expanding a symtab, pPerhaps something that cou=
ld
reproduce the problem:

1. Load your binary in GDB
2. Use the command "maintenance expand-symtabs".

--=20
You are receiving this mail because:
You are on the CC list for the bug.=