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] New: [ARMv7] [gdbserver] maybe_hw_step: Assertion `has_single_step_breakpoints (thread)' failed.
Date: Wed, 02 Nov 2022 15:50:07 +0000 [thread overview]
Message-ID: <bug-29742-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29742
Bug ID: 29742
Summary: [ARMv7] [gdbserver] maybe_hw_step: Assertion
`has_single_step_breakpoints (thread)' failed.
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: libin.dang at gmail dot com
Target Milestone: ---
The following GDBserver assertion failure happened:
../../gdb-13.0.50/gdbserver/linux-low.cc:2448: A problem internal to GDBserver
has been detected.
maybe_hw_step: Assertion `has_single_step_breakpoints (thread)' failed.
Aborted (core dumped)
Here is the hardware information:
> cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 533.33
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
processor : 1
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 533.33
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
Hardware : Xilinx Zynq Platform
Revision : 0003
Serial : 0000000000000000
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-02 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 15:50 libin.dang at gmail dot com [this message]
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
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@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).