public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/30387] gdbserver assert error on arm platform
Date: Thu, 11 May 2023 01:56:16 +0000	[thread overview]
Message-ID: <bug-30387-4717-xxfHpvmWDZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30387-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.marchi at polymtl dot ca

--- Comment #15 from Simon Marchi <simon.marchi at polymtl dot ca> ---
(In reply to Yan, Zhiyong from comment #14)
> (In reply to Luis Machado from comment #13)
> > I wonder if this also reproduces on x86. If so, that would make a better
> > case for urgency of fixing this.
> 
> This issue can't be produced on x86. I think it is because x86 supports
> hardware breakpoint. If make gdbserver use software breakpoint on x86, this
> issue can be produced.

I think you mean hardware single stepping, not hardware breakpoint.  GDB uses
software breakpoints for x86 as well as ARM.  But GDB uses hardware single
stepping for x86, and software single stepping for ARM (meaning it inserts a
breakpoint at the next instruction(s) and resumes when it wants to single
step).

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

  parent reply	other threads:[~2023-05-11  1:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  6:43 [Bug gdb/30387] New: " 2982971635 at qq dot com
2023-04-25  6:54 ` [Bug gdb/30387] " 2982971635 at qq dot com
2023-04-25  6:55 ` 2982971635 at qq dot com
2023-04-25  7:01 ` 2982971635 at qq dot com
2023-04-25  7:02 ` 2982971635 at qq dot com
2023-05-02  7:11 ` luis.machado at arm dot com
2023-05-02 14:17 ` [Bug server/30387] " luis.machado at arm dot com
2023-05-04  9:17 ` 2982971635 at qq dot com
2023-05-04 10:45 ` luis.machado at arm dot com
2023-05-05  2:20 ` 2982971635 at qq dot com
2023-05-05  2:22 ` 2982971635 at qq dot com
2023-05-10  7:41 ` 2982971635 at qq dot com
2023-05-10  7:52 ` luis.machado at arm dot com
2023-05-10  7:52 ` luis.machado at arm dot com
2023-05-10  9:16 ` 2982971635 at qq dot com
2023-05-11  1:56 ` simon.marchi at polymtl dot ca [this message]
2023-05-11  2:50 ` 2982971635 at qq dot com
2023-06-07 10:24 ` 2982971635 at qq dot com
2023-07-05 14:25 ` brobecker at gnat dot com
2023-07-05 14:33 ` luis.machado at arm dot com
2023-07-05 15:21 ` brobecker at gnat dot com
2023-08-08  2:59 ` kevinb at redhat dot com
2023-08-11 16:45 ` luis.machado at arm dot com
2023-08-11 17:33 ` kevinb at redhat dot com
2023-08-11 17:59 ` luis.machado at arm dot com
2023-08-12  2:38 ` kevinb at redhat dot com
2023-08-12  3:54 ` cvs-commit at gcc dot gnu.org
2023-08-12  4:02 ` kevinb at redhat 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-30387-4717-xxfHpvmWDZ@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).