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 644A3394743E; Tue,  1 Jun 2021 14:14:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 644A3394743E
From: "bernd.edlinger at hotmail dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/26096] gdb sets breakpoint at cold clone
Date: Tue, 01 Jun 2021 14:14:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-26096-4717-EKsxZ45Opt@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26096-4717@http.sourceware.org/bugzilla/>
References: <bug-26096-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: Tue, 01 Jun 2021 14:14:52 -0000

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

--- Comment #10 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Apparently I misunderstood your comment above:

> Either way, in absence of a fix in gcc for this, we could adapt a interpr=
etation
> that the entry pc is the start address of the first range. At least, this=
 works
> for this exec:

What I meant, is that currently the entry_pc is ignored at least when
you want to place a break point on an inline function.
Instead the start of the first subrange is used.

But the entry_pc is sometimes not the start of the first subrange,
but maybe the second or third.

My patch re-orders the sub-range so that the subrange that starts at
the entry_pc becomes the first one.

but I always looked at the breakpoint addresses:

(gdb) b <symbol>
(gdb) info b

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