Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
	gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [PATCH] Improved support for overlay breakpoints in ROM
Date: Tue, 05 Feb 2002 20:17:00 -0000	[thread overview]
Message-ID: <npit9bnsya.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3C608108.C7BA0407@redhat.com>

Michael Snyder <msnyder@redhat.com> writes:

> Jim Blandy wrote:
> > 
> > Typo:
> > 
> > > +     /* On the same principal, an overlay manager can arrange to call a
> > 
> > s/principal/principle/
> > 
> > It seems to me that, if overlay management is disabled, or set to
> > `manual', we shouldn't even set a breakpoint in _ovly_debug_event.
> 
> By analogy with the longjmp breakpoint, it seems easiest just to 
> create the breakpoint when the symbol file is loaded, and then
> enable/disable it as needed.  When it is disabled, it doesn't
> represent any significant overhead.

Okay, I see.

> > We need to document the new rules in the GDB manual.
> 
> Yep.  

... How can we prevent this from falling through the cracks?  I don't
mind doing it, but I'm afraid I'm going to forget.


  reply	other threads:[~2002-02-06  4:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04 16:18 Michael Snyder
2002-02-04 16:40 ` [RFA] " Michael Snyder
2002-02-05  3:14 ` [PATCH] " Eli Zaretskii
2002-02-05  9:54   ` Michael Snyder
2002-02-05 16:20 ` Jim Blandy
2002-02-05 17:11   ` Michael Snyder
2002-02-05 20:17     ` Jim Blandy [this message]
2002-02-07 11:44       ` Michael Snyder
2002-02-07 12:23         ` Eli Zaretskii
2002-02-07 16:40           ` Michael Snyder
2002-02-07 15:30         ` Andrew Cagney

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=npit9bnsya.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.com \
    --cc=msnyder@redhat.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