Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: gdb@sourceware.org
Subject: Re: RISC-V and fake function debug info in the testsuite
Date: Sat, 13 Apr 2019 18:18:00 -0000	[thread overview]
Message-ID: <CAFyWVab_VW7-Rz-E6_sJiU5V8DZgWYfzEMq1QCcT6WE61X4ktw@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaY+CMukKrSvtBAuxWQaFrm-WW3Ps2VOd+Xa6pRX4942XQ@mail.gmail.com>

On Fri, Apr 12, 2019 at 5:17 PM Jim Wilson <jimw@sifive.com> wrote:
> The question is what to do next.

On second thought, I realized I can fix it by wrapping the target
memory read in a try/catch.  I'm just not used to fixing problems that
way.  That defers the error from when we set the breakpoint to when we
try to run, at which point we get an error trying to write a
breakpoint instruction to an invalid address, which seems to be the
way that this works on other targets.  I already tried that and it
does fix the testsuite failures that I'm looking at.

Jim


      reply	other threads:[~2019-04-13 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13  0:17 Jim Wilson
2019-04-13 18:18 ` Jim Wilson [this message]

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=CAFyWVab_VW7-Rz-E6_sJiU5V8DZgWYfzEMq1QCcT6WE61X4ktw@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=gdb@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