From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 95C533851C12; Wed, 27 May 2020 13:33:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 95C533851C12 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1590586424; bh=nzKFyqSS7dTj1RNzU3r0XmsBh+d8HBliO9e+9OYC0yU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=I0lVUuSr4u+uLZ5Sms6LmhFP+OMk6TErX+ZgL6yFULw/gPvudFFyZZb+KXXt7OBx1 E0rxQsBwmFjjHn/B6KximlzEKZDZ50EgjsweOLS6JuQYbBf+cttLrfimpaO9liXod4 fbwLxzh2L+uWSJXSUoB/xBZcfqYdNlEt17kEFaYA= From: "yangyibiao at hust dot edu.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/95360] inconsistent behaviors at -O0 Date: Wed, 27 May 2020 13:33:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yangyibiao at hust dot edu.cn X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 13:33:44 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95360 --- Comment #6 from Yibiao Yang --- (In reply to Jonathan Wakely from comment #2) > (In reply to Yibiao Yang from comment #0) > > As showed, Line 6 is hit first and then hit Line 7 with stepi. > > However, when using step, gdb is first hit Line 7 and then hit Line 6. > > This is an inconsistent behaviors between stepi and step >=20 > Why is that a bug? Why is it a GCC bug? To be honest, I am not sure whether this is a gcc bug or a gdb bug. I am ve= ry sorry for that.=20 I report it here as I doubt that the line table is generated incorrectly by compilers.=