Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: jjohnstn@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: pending breakpoint support  [1/3]
Date: Sat, 07 Feb 2004 15:13:00 -0000	[thread overview]
Message-ID: <6654-Sat07Feb2004171356+0200-eliz@elta.co.il> (raw)
In-Reply-To: <y0mr7x8otd1.fsf@toenail.toronto.redhat.com> (fche@redhat.com)

> From: fche@redhat.com (Frank Ch. Eigler)
> Date: 06 Feb 2004 15:17:30 -0500
> 
> jjohnstn wrote:
> 
> > +* Pending breakpoint support
> > +
> > +Support has been added to allow specifying breakpoints in shared libraries
> > +that have not yet been loaded.  If a breakpoint location cannot be found,
> > +GDB queries you if you wish to make the breakpoint pending on a
> > +future shared-library load.  If and when GDB resolves the breakpoint symbol, 
> > +the pending breakpoint is removed as one or more regular breakpoints are
> > +created.  Pending breakpoints are very useful for gcj java debugging.
> 
> If I were to word this, it'd be something like:
> 
> GDB now supports specifying breakpoints in shared libraries that have
> not yet been loaded.  If GDB cannot find a breakpoint location the
> user specifies, it prompts for whether the breakpoint should be
> deferred, pending a future shared library load.  If and when GDB
> resolves the symbol, it replaces the pending breakpoint with a regular
> breakpoint.  This feature is very useful for gcj java and sid debugging.

Frank, I like your wording better.  Thanks.


      reply	other threads:[~2004-02-07 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 20:52 Jeff Johnston
2004-01-22 22:27 ` Daniel Jacobowitz
2004-01-27 20:41   ` J. Johnston
2004-01-30  4:13     ` Daniel Jacobowitz
2004-01-30 18:51       ` Jeff Johnston
2004-01-30 19:09         ` Daniel Jacobowitz
2004-01-30 22:46           ` Jeff Johnston
2004-01-30 23:45             ` Daniel Jacobowitz
2004-01-31  0:33               ` Jeff Johnston
2004-02-02 21:12                 ` Jeff Johnston
2004-02-02 21:22                   ` Daniel Jacobowitz
2004-02-02 22:18                     ` Jeff Johnston
2004-02-02 22:21                       ` Daniel Jacobowitz
2004-02-03  6:07                       ` Eli Zaretskii
2004-02-05 21:33                         ` Jeff Johnston
2004-02-06 20:17                           ` Frank Ch. Eigler
2004-02-07 15:13                             ` Eli Zaretskii [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=6654-Sat07Feb2004171356+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=fche@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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