public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "2982971635 at qq dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30387] New: gdbserver assert error on arm platform Date: Tue, 25 Apr 2023 06:43:52 +0000 [thread overview] Message-ID: <bug-30387-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30387 Bug ID: 30387 Summary: gdbserver assert error on arm platform Product: gdb Version: HEAD Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: 2982971635 at qq dot com Target Milestone: --- Created attachment 14848 --> https://sourceware.org/bugzilla/attachment.cgi?id=14848&action=edit This app can produce gdbserver assert error on arm platform Hi, Attached gdbserver-test-app.tar can produce gdbserver assert error on arm platform. This issue happens on gdb any version until last git tree master branch. Below is version and error message. I will add produce step specification in next comment. Best Regards. Zhiyong root@xilinx-zynq:~# gdb -v GNU gdb (GDB) 14.0.50.20230421-git Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. root@xilinx-zynq:~# root@xilinx-zynq:~# gdbserver --version GNU gdbserver (GDB) 14.0.50.20230421-git Copyright (C) 2023 Free Software Foundation, Inc. gdbserver is free software, covered by the GNU General Public License. This gdbserver was configured as "arm-wrs-linux-gnueabi" 2389.242477 [threads] resume_one_lwp_throw: Resuming lwp 448 (continue, signal 0, stop not expected) ../../git/gdbserver/linux-low.cc:2448: A problem internal to GDBserver has been detected. maybe_hw_step: Assertion `has_single_step_breakpoints (thread)' failed. Aborted -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-04-25 6:43 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 6:43 2982971635 at qq dot com [this message] 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 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@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: linkBe 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).