From: Daniel Jacobowitz <drow@mvista.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: pending breakpoint support [1/3]
Date: Mon, 02 Feb 2004 22:21:00 -0000 [thread overview]
Message-ID: <20040202222114.GA15928@nevyn.them.org> (raw)
In-Reply-To: <401ECCB2.2010205@redhat.com>
On Mon, Feb 02, 2004 at 05:18:26PM -0500, Jeff Johnston wrote:
> Daniel Jacobowitz wrote:
>
> >On Mon, Feb 02, 2004 at 04:12:17PM -0500, Jeff Johnston wrote:
> >
> >
> >>Patch checked in. I have included the final patch here with the
> >>reworded message.
> >>
> >>
> >
> >I suspect this deserves a NEWS entry. Mind taking care of that?
> >
> >
> Ok, how about the accompanying patch?
OK. And here I had no idea you were working on gcj support...
>
> -- Jeff J.
>
> 2004-02-02 Jeff Johnston <jjohnstn@redhat.com>
>
> * NEWS: Add information about new pending breakpoint support.
>
>
> Index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.134
> diff -u -r1.134 NEWS
> --- NEWS 22 Jan 2004 23:18:03 -0000 1.134
> +++ NEWS 2 Feb 2004 22:16:45 -0000
> @@ -3,6 +3,15 @@
>
> *** Changes since GDB 6.0:
>
> +* 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,
> +you are queried to see if you wish to make the breakpoint pending on a
> +future shared-library load. If and when the breakpoint symbol is resolved,
> +the pending breakpoint is removed as one or more regular breakpoints are
> +created. Pending breakpoints are very useful for gcj java debugging.
> +
> * Removed --with-mmalloc
>
> Support for the mmalloc memory manager has been removed, as it
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-02 22:21 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 [this message]
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
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=20040202222114.GA15928@nevyn.them.org \
--to=drow@mvista.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