public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, simon.marchi@polymtl.ca,
	tdevries@suse.de, kevinb@redhat.com, ro@cebitec.uni-bielefeld.de,
	luis.machado@linaro.org
Subject: Re: GDB 11 branching update (2021-05-30)
Date: Thu, 3 Jun 2021 22:44:17 +0100	[thread overview]
Message-ID: <20210603214417.GQ2672@embecosm.com> (raw)
In-Reply-To: <20210530142408.GA1313865@adacore.com>

* Joel Brobecker <brobecker@adacore.com> [2021-05-30 07:24:08 -0700]:

>   * [AndrewB/Simon] <PR gdb/26819>
>     Bug 26819 - RISC-V: internal-error: int finish_step_over(execution_control_state*): Assertion
>     https://sourceware.org/bugzilla/show_bug.cgi?id=26819
> 
>     I think the situation has been improved thanks to a couple of
>     patches, but the user still has some scenarios where the issue
>     happens.

I've reviewed the latest reports from the user, and posted some
comments to the bug report.

In summary I think the issues the user was seeing were due to openocd
being miss-configured.  There probably is something we could fix in
GDB so that we give an error rather than triggering an assertion, but
I don't think this should be a blocker for the release.

I would of course, welcome people to review my analysis, and provide
additional insight.

Thanks,
Andrew

  parent reply	other threads:[~2021-06-03 21:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 14:24 Joel Brobecker
2021-05-31 15:53 ` John Baldwin
2021-06-04 16:08   ` John Baldwin
2021-06-04 17:06     ` Joel Brobecker
2021-06-03 21:44 ` Andrew Burgess [this message]
2021-06-04 13:24   ` Joel Brobecker
2021-06-04 22:45 ` Kevin Buettner
2021-06-08  8:40   ` Florian Weimer
2021-06-08 17:04     ` Simon Marchi
2021-06-08 20:53       ` Simon Marchi
2021-06-09  6:37         ` Florian Weimer
2021-06-11 21:51           ` Simon Marchi
2021-06-26  9:27             ` Florian Weimer

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=20210603214417.GQ2672@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=luis.machado@linaro.org \
    --cc=ro@cebitec.uni-bielefeld.de \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    /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).