Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pgilliam@us.ibm.com, gdb@sources.redhat.com
Subject: Re: What should be used instead of deprecated_read_memory_nobpt()?
Date: Tue, 29 Nov 2005 22:14:00 -0000	[thread overview]
Message-ID: <20051129220752.GQ954@adacore.com> (raw)
In-Reply-To: <200511292204.jATM4R1s022362@elgar.sibelius.xs4all.nl>

> Not sure, but read_memory_unsigned_integer() might not be safe,
> because of the possibility of inserted breakpoints.

Are there targets that do not remove breakpoints when the target stops?

-- 
Joel


  reply	other threads:[~2005-11-29 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 22:04 Paul Gilliam
2005-11-29 22:07 ` Mark Kettenis
2005-11-29 22:14   ` Joel Brobecker [this message]
2005-11-30  1:36     ` Daniel Jacobowitz
2005-11-30  1:38       ` Jim Blandy
2005-11-30 23:17         ` Paul Gilliam
2005-12-07  2:12           ` Andrew Cagney
2005-11-29 22:15   ` Daniel Jacobowitz

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=20051129220752.GQ954@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pgilliam@us.ibm.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