From: Jeff Johnston <jjohnstn@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: pending breakpoint support [1/3]
Date: Thu, 05 Feb 2004 21:33:00 -0000 [thread overview]
Message-ID: <4022B6B8.4020400@redhat.com> (raw)
In-Reply-To: <u1xpck83g.fsf@elta.co.il>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Eli Zaretskii wrote:
>>Date: Mon, 02 Feb 2004 17:18:26 -0500
>>From: Jeff Johnston <jjohnstn@redhat.com>
>>
>>Ok, how about the accompanying patch?
>>
>>-- Jeff J.
>>
>>2004-02-02 Jeff Johnston <jjohnstn@redhat.com>
>>
>> * NEWS: Add information about new pending breakpoint support.
>
>
> Thanks. Is it possible to modify the wording so that it doesn't use
> passive tense so much? I'm told by native English speakers that
> passive is BAD...
>
> For example, this:
>
>
>>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.
>
>
> could be rephrased like this:
>
> If a breakpoint location cannot be found, GDB queries you if you
> wish to make the breakpoint pending on ...
>
> Etc., you get the point.
>
> TIA
>
>
Is the attached ok to commit?
[-- Attachment #2: news.patch --]
[-- Type: text/plain, Size: 852 bytes --]
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.135
diff -u -r1.135 NEWS
--- NEWS 5 Feb 2004 19:56:33 -0000 1.135
+++ NEWS 5 Feb 2004 21:31:35 -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,
+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.
+
* Removed --with-mmalloc
Support for the mmalloc memory manager has been removed, as it
next prev parent reply other threads:[~2004-02-05 21:33 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 [this message]
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=4022B6B8.4020400@redhat.com \
--to=jjohnstn@redhat.com \
--cc=drow@mvista.com \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.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