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/31070] Abnormal Jump in Execution for builtin function using 'stepi' Command in GDB Date: Thu, 16 Nov 2023 08:33:00 +0000 [thread overview] Message-ID: <bug-31070-4717-a8OAZhZ3rL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31070-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31070 --- Comment #3 from Anonymous <iamanonymous.cs at gmail dot com> --- I have verified that the latest trunk versions of GCC and GDB still exhibit the same problem. $ gcc --version gcc (GCC) 14.0.0 20231116 (experimental) Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ gdb --version GNU gdb (GDB) 15.0.50.20231116-git Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-16 8:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-16 7:24 [Bug gdb/31070] New: " iamanonymous.cs at gmail dot com 2023-11-16 7:25 ` [Bug gdb/31070] " iamanonymous.cs at gmail dot com 2023-11-16 7:27 ` iamanonymous.cs at gmail dot com 2023-11-16 7:28 ` iamanonymous.cs at gmail dot com 2023-11-16 8:26 ` iamanonymous.cs at gmail dot com 2023-11-16 8:33 ` iamanonymous.cs at gmail dot com [this message] 2023-11-16 11:36 ` vries at gcc dot gnu.org 2023-11-16 11:54 ` iamanonymous.cs at gmail dot com 2023-11-16 11:56 ` vries at gcc dot gnu.org 2023-11-16 11:59 ` 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-31070-4717-a8OAZhZ3rL@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: linkBe 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).