Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Don Howard <dhoward@redhat.com>
To: Paul Vogelezang <pvogelez@HISCOM.NL>
Cc: <gdb@sources.redhat.com>
Subject: Re: No breakpoints in memory area
Date: Wed, 19 Jun 2002 10:13:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0206191007370.3839-100000@theotherone> (raw)
In-Reply-To: <02Jun19.160712cest.119053@ns.hiscom.nl>

On Wed, 19 Jun 2002, Paul Vogelezang wrote:

> Hi,
> 
> I'd like to know if it is possible to tell GDB that a certain area of
> memory is readonly. The area is located in a shared memory segment and
> contains executable code. I want to tell GDB that it is not allowed to
> set any breakpoints in that area.
> 
> I hope somebody can help me with this.
> 

mem <start> <end> ro

See also 'help mem' and
http://sources.redhat.com/gdb/current/onlinedocs/gdb_9.html#SEC63



-- 
dhoward@redhat.com
gdb engineering



      reply	other threads:[~2002-06-19 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19  6:59 Paul Vogelezang
2002-06-19 10:13 ` Don Howard [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=Pine.LNX.4.33.0206191007370.3839-100000@theotherone \
    --to=dhoward@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=pvogelez@HISCOM.NL \
    /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