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 966283858CD9; Sat,  8 Jun 2024 04:07:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 966283858CD9
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1717819656;
	bh=QIXiZssQcf6Yip3CWfs6l5NiaghzcN/nom4s8oiCOAQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=LwsJ3oYr3qBYofeSupM7DnTCw1snCP9KhnToFzj9nZ2AuvmcZnoDedq4UjoFO0Ws4
	 BExzjF/K0H0GvjDkop5cHfBJOAa+cpCN4//DLYPacoVjCDH3aNtdedNcuuiSU/HNrU
	 4dVsq9zveKyAoV3JpAg0Wu3TPKShDofkq+wh+LdI=
From: "iamanonymous.cs at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31849] Issue with Unexpected Behavior in GDB Stepping at
 Optimization Level O2 and O3
Date: Sat, 08 Jun 2024 04:07:35 +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: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iamanonymous.cs 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-31849-4717-LIuLOukVp2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31849-4717@http.sourceware.org/bugzilla/>
References: <bug-31849-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
List-Id: <gdb-prs.sourceware.org>

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

--- Comment #5 from Anonymous <iamanonymous.cs at gmail dot com> ---
(In reply to Tom Tromey from comment #3)
> You should probably attach your executable, since this is
> most likely compiler dependent.
>=20
> One suggestion is to examine the line table and see what it says.
> Often this kind of behavior ends up being gdb doing what the
> compiler said to do.

Thanks for your reply. I have attached the executable the can reproduce this
potential issue.

It seems that Line 15, 25, 26 are both mapped to the same address of
0x00000000004011d0.

Does this indicate that this is a gcc issue?

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