public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: William Tambe <tambewilliam@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Is it possible to support gdb command hbreak with target sim ?
Date: Tue, 29 Sep 2020 09:46:53 +0100	[thread overview]
Message-ID: <20200929084653.GB1540867@embecosm.com> (raw)
In-Reply-To: <CAF8i9mN9_H0eTM11wYmbOfNxGT2Hf8tDZtpL7fghD94P+Na_hw@mail.gmail.com>

* William Tambe via Gdb <gdb@sourceware.org> [2020-09-28 21:29:26 -0500]:

> Is it possible to support gdb command hbreak with target sim ?

There's currently no support for hardware breakpoints in the simulator
target, instead only software breakpoints are supported where GDB
takes responsibility for reading and backing up the old memory
contents before writing in a software breakpoint instruction.

This doesn't mean that hardware breakpoint support couldn't be added.

Thanks,
Andrew

  reply	other threads:[~2020-09-29  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  2:29 William Tambe
2020-09-29  8:46 ` Andrew Burgess [this message]
2021-01-13  5:46   ` Mike Frysinger
2021-01-13 11:08     ` Mike Frysinger

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=20200929084653.GB1540867@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb@sourceware.org \
    --cc=tambewilliam@gmail.com \
    /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).