From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/rfc] More 6.1.1 NEWS updates
Date: Sat, 12 Jun 2004 17:53:00 -0000 [thread overview]
Message-ID: <40CB431D.7000308@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
I went to mention the pending breakpoint fix but found that pending
breakpoints hadn't been announced! This should be it for NEWS entries.
comments?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2052 bytes --]
2004-06-12 Andrew Cagney <cagney@gnu.org>
* NEWS: Describe the problems fixed by the location-expression,
and DW_EH_PE_funcrel changes. Mention pending breakpoints (based
on earlier posts from Jeff Johnston and Eli Zaretskii).
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.138.2.7
diff -p -u -r1.138.2.7 NEWS
--- NEWS 11 Jun 2004 18:37:33 -0000 1.138.2.7
+++ NEWS 12 Jun 2004 17:51:22 -0000
@@ -3,6 +3,18 @@
*** Changes in GDB 6.1.1:
+* Pending breakpoint support (also included in GDB 6.1)
+
+Support has been added to allow you to specify breakpoints in shared
+libraries that have not yet been loaded. If a breakpoint location
+cannot be found, and the "breakpoint pending" option is set to auto,
+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.
+
* Fixed ISO-C build problems
The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
@@ -25,10 +37,17 @@ systems (Solaris, IRIX). Ref: server/51
Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
has been updated to use constant array sizes.
-* Bug fixes
+* Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
+
+GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
+its generated DWARF Call Frame Info. This encoding was causing GDB to
+panic, that panic has been fixed. Ref: gdb/1628.
+
+* Fixed a problem when examining parameters in shared library code.
-gdb/1628: GDB now handles the DW_EH_PE_funcrel encoding in DWARF Call
-Frame Info.
+When examining parameters in optimized shared library code generated
+by a mainline GCC, GDB would incorrectly report ``Variable "..." is
+not available''. GDB now correctly displays the variable's value.
*** Changes in GDB 6.1:
next reply other threads:[~2004-06-12 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 17:53 Andrew Cagney [this message]
2004-06-13 4:05 ` Eli Zaretskii
2004-06-14 13:39 ` 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=40CB431D.7000308@gnu.org \
--to=cagney@gnu.org \
--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