public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qwertytmp1 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28717] New: GDB steps twice on a single stepi
Date: Mon, 20 Dec 2021 16:20:52 +0000	[thread overview]
Message-ID: <bug-28717-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28717
           Summary: GDB steps twice on a single stepi
           Product: gdb
           Version: 11.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: qwertytmp1 at gmail dot com
  Target Milestone: ---

On ARM/aarch64 platform, when executing command:
```
stepi
```

address increases by 8 bytes, instead of 4.

When I printed packets, received from the DGB client, I've found that it
consists of strange workflow:

```
'm1e2f8,4'    - read 4 bytes memory at 0x1e2f8
'vCont?'      - request a list of actions supported by the ‘vCont’ packet.
'vCont;s:1;c' - resume the inferior, singlestep, continue.
'g'           - return the value of the CPU registers
'm1e2fc,4'    - read 4 bytes memory at 0x1e2fc
'vCont;s:1'   - resume the inferior, singlestep.
'g'           - return the value of the CPU registers
...
```

As it can be seen, we have 'vCont;s:1;c' and 'vCont;s:1'.

P.S. Problem exists as on gdb-9.1 as on the gdb-11.1.

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

             reply	other threads:[~2021-12-20 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 16:20 qwertytmp1 at gmail dot com [this message]
2021-12-20 19:38 ` [Bug gdb/28717] " simark at simark dot ca
2021-12-21 11:07 ` qwertytmp1 at gmail dot com
2021-12-23 11:43 ` qwertytmp1 at gmail dot com
2021-12-26 18:01 ` tromey at sourceware dot org
2021-12-28 10:47 ` qwertytmp1 at gmail dot com
2021-12-28 16:37 ` qwertytmp1 at gmail dot com
2022-03-06 17:04 ` tromey at sourceware dot org

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-28717-4717@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).