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 D5FDC3942014; Mon, 19 Apr 2021 11:55:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D5FDC3942014
From: "cn.yiki at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27743] Internal error psymtab.c
Date: Mon, 19 Apr 2021 11:55:56 +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: cn.yiki at gmail 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: 
Message-ID: <bug-27743-4717-kztjgztrdR@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 11:55:57 -0000

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

--- Comment #11 from Ethan Zhang <cn.yiki at gmail dot com> ---
I have found it to be related to link time optimization and setting a break
point with absolute path.

Compile a piece of source code with gcc9 using link time optimization, for
example:
    g++-9 -ggdb -flto test.cpp -o test

Load "test" into GDB 10, then set break point using absolute path:
    break /path/to/test:(line number)

That should be enough to reproduce the issue.

And it seems to only appear when the program is compiled with gcc9 with lto,
debug using gdb10 and have a break point set in absolute path.

The content of the source code doesn't seem to make a difference.
If the source code is compiled in gcc10 with lto, this issue doesn't appear.
If the break point is set through relative path, this issue doesn't appear.

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