public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ahmedsayeed1982 at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/27009] [s390] GDB branches randomly for BC instruction while displaced stepping
Date: Sun, 27 Jun 2021 17:59:57 +0000 [thread overview]
Message-ID: <bug-27009-4717-sWyJ9pFt9t@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27009-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27009
Ahmed Sayeed <ahmedsayeed1982 at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ahmedsayeed1982 at yahoo dot com
--- Comment #4 from Ahmed Sayeed <ahmedsayeed1982 at yahoo dot com> ---
.align 8
.globl main
.globl insn
.type main, @function
.type insn, @function
# This should return 0 on success.
main:
basr %r1, %r0
insn: bc 15, win-insn(0,%r1)
lghi %r2,1
win: lghi %r2,0
br %r14
Assemble and link the above.
Turn on displaced stepping, set a breakpoint on `insn`, run, then try to step
over the breakpoint with stepi.
(gdb) set displaced-stepping on
(gdb) b insn
(gdb) r
(gdb) stepi
http://ooviv.xyz/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-27 17:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 23:07 [Bug breakpoints/27009] New: " gfrix98 at gmail dot com
2020-12-03 23:09 ` [Bug breakpoints/27009] " gfrix98 at gmail dot com
2020-12-06 10:28 ` cvs-commit at gcc dot gnu.org
2020-12-06 10:29 ` brobecker at gnat dot com
2020-12-06 10:31 ` cvs-commit at gcc dot gnu.org
2021-01-31 6:26 ` brobecker at gnat dot com
2021-06-27 17:59 ` ahmedsayeed1982 at yahoo dot com [this message]
2021-08-10 12:45 ` ucelsanicin at yahoo dot com
2021-09-02 11:06 ` donipah907 at mtlcz dot com
2021-09-02 11:15 ` mark at klomp dot org
2021-09-06 9:09 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:38 ` mehmetgelisin at aol dot com
2021-09-22 10:11 ` diheto5497 at secbuf dot com
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-17 19:51 ` vmireskazki at gmail dot com
2021-10-19 7:15 ` progonsaytu at gmail dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-11-06 21:13 ` paneki8601 at dukeoo dot com
2021-11-16 19:08 ` xecana8007 at funboxcn dot com
2021-11-16 19:12 ` xecana8007 at funboxcn dot com
2021-11-16 19:15 ` xecana8007 at funboxcn dot com
2021-11-22 7:39 ` gexed96894 at keagenan 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-27009-4717-sWyJ9pFt9t@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).