From: Jim Wilson <jimw@sifive.com>
To: gdb@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Re: RISC-V: decr_pc_after_break causing problems
Date: Wed, 04 Jul 2018 00:17:00 -0000 [thread overview]
Message-ID: <CAFyWVaZ2_CTM2rL0OMv2V8R_0L52rUVOTgxuZ5Er9mW+Qw-+Jw@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaYoF8LmH=RGEZTrMWqaYF0i3GERZG-B_rDxtTt2LQs9gw@mail.gmail.com>
On Mon, Jun 25, 2018 at 7:54 PM, Jim Wilson <jimw@sifive.com> wrote:
> The RISC-V port in the riscv-tdep.c file has
> set_gdbarch_decr_pc_after_break (gdbarch, (has_compressed_isa ? 2 : 4));
I'm still hoping to get a response to this. I need to make
coordinated fixes to both gdb and the linux kernel to get breakpoints
working correctly.
Jim
next prev parent reply other threads:[~2018-07-04 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 2:54 Jim Wilson
2018-06-26 19:15 ` Tim Newsome
2018-07-04 0:17 ` Jim Wilson [this message]
2018-07-04 0:35 ` Palmer Dabbelt
2018-07-05 22:54 ` John Baldwin
2018-07-11 14:52 ` Andrew Burgess
2018-07-11 17:47 ` Andrew Burgess
2018-07-11 18:20 ` Jim Wilson
2018-07-16 22:09 ` Jim Wilson
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=CAFyWVaZ2_CTM2rL0OMv2V8R_0L52rUVOTgxuZ5Er9mW+Qw-+Jw@mail.gmail.com \
--to=jimw@sifive.com \
--cc=andrew.burgess@embecosm.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