Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>
Cc: Anton Kolesov <Anton.Kolesov@synopsys.com>,
	Shahab Vahedi <shahab@synopsys.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Francois Bedard <fbedard@synopsys.com>
Subject: Re: [PATCH] arc: Add support for Linux coredump files
Date: Tue, 29 Sep 2020 17:42:20 +0200	[thread overview]
Message-ID: <20200929154220.GD4717@gmail.com> (raw)
In-Reply-To: <81e2fb09-4d5f-a274-8986-2726a45d4290@simark.ca>

Hi Simon,

First, thank you a lot for such explanatory answer.

On Tue, Sep 29, 2020 at 10:22:18AM -0400, Simon Marchi wrote:
> target_read_memory calls read_inferior_memory, which calls the target's
> read_memory method, and then puts back in place the instructions
> shadowed by breakpoints and fast tracepoint jumps inserted by GDBserver
> in place.  This is so that the memory returned to the caller (and
> possibly to GDB) contains the contents it expects to see.

I repeat the code snippet here:
----
bool
arc_target::low_breakpoint_at (CORE_ADDR where)
{
  uint16_t insn;
  uint16_t breakpoint = ntohs (TRAP_S_1_OPCODE);

  target_read_memory (where, (gdb_byte *) &insn, TRAP_S_1_SIZE);
  return (insn == breakpoint);
}
----

Because this memory access is indeed to check for a "breakpoint",
then I should NOT be using breakpoint-undoing edition.  Therefore,
I will use "this->read_memory (...)".


Cheers,
Shahab

  reply	other threads:[~2020-09-29 15:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 11:27 Shahab Vahedi
2020-09-07  9:14 ` Shahab Vahedi
2020-09-16  2:31 ` [PING^2][PATCH] " Shahab Vahedi
2020-09-16 20:21 ` [PATCH] " Simon Marchi
2020-09-17 11:55   ` Aktemur, Tankut Baris
2020-09-28 13:47     ` Shahab Vahedi via Gdb-patches
2020-09-28 14:08       ` Aktemur, Tankut Baris via Gdb-patches
2020-09-28 19:10         ` Simon Marchi
2020-09-29  8:24           ` Shahab Vahedi via Gdb-patches
2020-09-29  9:02             ` Shahab Vahedi via Gdb-patches
2020-09-29 14:22             ` Simon Marchi
2020-09-29 15:42               ` Shahab Vahedi via Gdb-patches [this message]
2020-10-01 13:30   ` Shahab Vahedi via Gdb-patches
2020-09-29 16:15 ` [PATCH v2] " Shahab Vahedi via Gdb-patches
2020-10-05  2:13   ` Simon Marchi
2020-10-07 16:11 ` [PUSHED master] " Shahab Vahedi via Gdb-patches
2020-10-07 16:32 ` [PUSHED gdb-10-branch] " Shahab Vahedi via Gdb-patches

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=20200929154220.GD4717@gmail.com \
    --to=gdb-patches@sourceware.org \
    --cc=Anton.Kolesov@synopsys.com \
    --cc=fbedard@synopsys.com \
    --cc=shahab.vahedi@gmail.com \
    --cc=shahab@synopsys.com \
    --cc=simark@simark.ca \
    /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