public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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: Wed, 05 Jun 2024 16:16:00 +0000	[thread overview]
Message-ID: <bug-31849-4717-C8pEn33ghW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31849-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Anonymous <iamanonymous.cs at gmail dot com> ---
(In reply to Anonymous from comment #1)
> Additionally, this unexpected stepping behavior does not occur when the
> program is compiled with optimization level O0.

We found this issue by comparing the executable files compiled with
optimization level O2, when comparing the debugging traces at the source level
and the instruction level.

We know that since optimization will optimize a large amount of code, the hit
information (i.e., the lines of code that the debugger stops at) of executable
files generated with different optimization levels under GDB cannot be directly
compared.

Here, "this unexpected stepping behavior does not occur" indicates that, at the
O0 level, neither the source-level debugging nor the instruction-level
debugging encountered the unexpected stopping at line #17.

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

  parent reply	other threads:[~2024-06-05 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 15:59 [Bug gdb/31849] New: " iamanonymous.cs at gmail dot com
2024-06-05 15:59 ` [Bug gdb/31849] " iamanonymous.cs at gmail dot com
2024-06-05 16:02 ` iamanonymous.cs at gmail dot com
2024-06-05 16:16 ` iamanonymous.cs at gmail dot com [this message]
2024-06-06 14:29 ` tromey at sourceware dot org
2024-06-08  4:00 ` iamanonymous.cs at gmail dot com
2024-06-08  4:07 ` iamanonymous.cs at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31849-4717-C8pEn33ghW@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).