public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jmatyas at codasip dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26819] RISC-V: internal-error: int finish_step_over(execution_control_state*): Assertion Date: Sat, 16 Jan 2021 11:00:46 +0000 [thread overview] Message-ID: <bug-26819-4717-IctStZy0XU@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26819-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26819 Jan Matyas <jmatyas at codasip dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #13 from Jan Matyas <jmatyas at codasip dot com> --- Hello, I have finally managed to re-test the updated code. I am sorry to report back that the issue appears not yet fully resolved. Re-running the GDB test scenarios in which this issue was originally encountered (that is: https://github.com/riscv/riscv-tests/tree/master/debug) now triggers a different assert. (1) In many of the above test scenarios, it is the following assert that gets triggered immediately after connecting GDB to the remote server, i.e. OpenOCD. OpenOCD is at that point already connected to the underlying target, which is the Spike RISC-V ISA simulator: (gdb) target extended-remote localhost:44553 Remote debugging using localhost:44553 warning: No executable has been specified and target does not support determining executable automatically. Try using the "file" command. ../../../binutils-gdb/gdb/remote.c:7820: internal-error: ptid_t remote_target::select_thread_for_ambiguous_stop_reply(const target_waitstatus*): Assertion `first_resumed_thread != nullptr' failed. A full log from one such test run is attached - 20210116-101128-spike32-CheckMisa.log. It shows the steps to reproduce the issue - most importantly the cmdline arguments to start Spike and OpenOCD. (2) There was one test run in which the original assert was encountered: ../../../binutils-gdb/gdb/infrun.c:5614: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. It is recorded in file: 20210116-101308-spike32_2-ProgramSwWatchpoint.log The revisions of Spike ISA sim, OpenOCD and gdb-binutils that I used were in all cases the latest HEADs as of now: - binutils-gdb: 68b007788a (Fri Jan 15 18:07:07 2021 -0800) - Spike: 35d50bc (Thu Jan 14 09:43:04 2021 -0800) - OpenOCD: ed37337b0 Please let me know if any further information is needed for reproduction or if you'd like me to re-test any other scenario. Best regards, Jan -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-16 11:00 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-30 16:11 [Bug gdb/26819] New: " jmatyas at codasip dot com 2020-10-30 16:13 ` [Bug gdb/26819] " jmatyas at codasip dot com 2020-11-08 9:07 ` [Bug gdb/26819] RISC-V: " jmatyas at codasip dot com 2020-11-08 10:07 ` andrew.burgess at embecosm dot com 2020-11-08 11:10 ` jmatyas at codasip dot com 2020-11-08 11:13 ` jmatyas at codasip dot com 2020-11-09 9:51 ` andrew.burgess at embecosm dot com 2021-01-06 6:37 ` jmatyas at codasip dot com 2021-01-06 9:35 ` andrew.burgess at embecosm dot com 2021-01-08 11:03 ` jmatyas at codasip dot com 2021-01-08 16:09 ` simark at simark dot ca 2021-01-14 1:27 ` cvs-commit at gcc dot gnu.org 2021-01-14 1:29 ` simark at simark dot ca 2021-01-14 9:11 ` andrew.burgess at embecosm dot com 2021-01-14 9:41 ` jmatyas at codasip dot com 2021-01-16 11:00 ` jmatyas at codasip dot com [this message] 2021-01-16 11:03 ` jmatyas at codasip dot com 2021-01-16 11:04 ` jmatyas at codasip dot com 2021-01-17 3:36 ` simark at simark dot ca 2021-01-17 22:37 ` jmatyas at codasip dot com 2021-01-17 22:38 ` jmatyas at codasip dot com 2021-01-17 22:39 ` jmatyas at codasip dot com 2021-01-18 5:15 ` simark at simark dot ca 2021-01-18 11:01 ` jmatyas at codasip dot com 2021-01-18 15:23 ` sebastian.huber@embedded-brains.de 2021-01-27 12:35 ` jmatyas at codasip dot com 2021-01-27 16:00 ` simark at simark dot ca 2021-02-07 21:20 ` jmatyas at codasip dot com 2021-02-08 2:00 ` simon.marchi at polymtl dot ca 2021-02-08 2:02 ` simon.marchi at polymtl dot ca 2021-02-20 20:51 ` simark at simark dot ca 2021-02-24 9:17 ` jmatyas at codasip dot com 2021-02-25 7:41 ` jmatyas at codasip dot com 2021-02-25 20:50 ` simark at simark dot ca 2021-03-04 23:23 ` jmatyas at codasip dot com 2021-03-04 23:24 ` jmatyas at codasip dot com 2021-03-04 23:25 ` jmatyas at codasip dot com 2021-03-04 23:25 ` jmatyas at codasip dot com 2021-03-04 23:27 ` simark at simark dot ca 2021-03-04 23:46 ` jmatyas at codasip dot com 2021-03-04 23:49 ` jmatyas at codasip dot com 2021-06-03 20:41 ` andrew.burgess at embecosm dot com 2021-06-03 21:19 ` andrew.burgess at embecosm dot com 2021-06-03 21:38 ` andrew.burgess at embecosm dot com 2021-06-06 14:28 ` brobecker at gnat dot com 2021-06-07 5:28 ` jmatyas at codasip dot com 2021-06-07 8:30 ` andrew.burgess at embecosm dot com 2021-08-06 1:41 ` lennordocdoc0921 at gmail dot com 2022-04-09 15:07 ` [Bug tdep/26819] " tromey at sourceware dot org 2022-11-29 19:38 ` 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-26819-4717-IctStZy0XU@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).