public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "libin.dang at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29742] [ARMv7] [gdbserver] maybe_hw_step: Assertion `has_single_step_breakpoints (thread)' failed.
Date: Thu, 10 Nov 2022 10:45:25 +0000	[thread overview]
Message-ID: <bug-29742-4717-5IJLKPrRwd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29742-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Libin Dang <libin.dang at gmail dot com> ---
(In reply to Luis Machado from comment #3)
> Understood. Can you share the remote traffic between gdbserver and gdb?
> 
> set debug remote 1
> set debug remote-packet-max-chars -1

We managed to reduce the reproduce session to this minimal one:

handle SIG32 nostop noprint
handle SIGSTOP nostop noprint

b vic_ar_work.c:2823

c
n
n
n
n
n

It may need a few less or more `next' commands to trigger this issue.

The outputs of debug remote for both host and target sides are attached.

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

  parent reply	other threads:[~2022-11-10 10:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 15:50 [Bug gdb/29742] New: " libin.dang at gmail dot com
2022-11-03  8:32 ` [Bug gdb/29742] " luis.machado at arm dot com
2022-11-03 15:33 ` libin.dang at gmail dot com
2022-11-03 16:45 ` luis.machado at arm dot com
2022-11-10 10:35 ` libin.dang at gmail dot com
2022-11-10 10:37 ` libin.dang at gmail dot com
2022-11-10 10:45 ` libin.dang at gmail dot com [this message]
2022-11-21 16:25 ` libin.dang at gmail dot com
2022-11-29 13:19 ` jeroen.hiddink at vialis dot nl
2023-02-10 14:45 ` libin.dang at gmail dot com
2023-02-10 14:47 ` libin.dang at gmail dot com
2023-02-10 14:50 ` libin.dang 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-29742-4717-5IJLKPrRwd@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).