[Crosstoolchain-logs] [SCM] GNU GDB Debian packaging repository branch, master, updated. debian/7.6-3-25-g41eb07a

[Samuel Bronson]

The following commit has been merged in the master branch:
commit 41eb07ad5fe8c93ef391978412e21d1ff12e0319
Author: Samuel Bronson <naesten at gmail.com>
Date:   Sun Jun 16 00:10:14 2013 -0400

    Drop dwarf2-cfi-warning.patch and linux-clear-thread-list.patch
    
    They seem to have outlived their usefulness.

diff --git a/debian/patches/dwarf2-cfi-warning.patch b/debian/patches/dwarf2-cfi-warning.patch
deleted file mode 100644
index 327cebe..0000000
--- a/debian/patches/dwarf2-cfi-warning.patch
+++ /dev/null
@@ -1,36 +0,0 @@
-Status: Unsuitable for upstream (at least, without a lot of arguing).
-
-GCC does not specify the state of every last register in the CIE.  Since
-GCC's focus is on correctness of runtime unwinding, any registers which
-have to be unwound will be specified; but unmodified registers will not
-be explicitly marked.  (How about modified, call-clobbered registers?
-I'm not sure if they are marked as unavailable.)
-
-GDB issues a noisy warning about this.  The warning is generally not useful,
-and we can get it extremely frequently (any time we load a new CIE).
-
-This patch disables the warning.  Alternately we could set the complaints
-threshold to zero, or implement a default frame init-register method for
-every architecture.  But someday the compiler will support using different
-calling conventions for internal functions, so that's not much of a stopgap. 
-ARM has a complex algorithm for handling this, involving scanning all CIEs -
-benefit not completely clear outside of the ARM context of flexible register
-sets.
-
----
- gdb/dwarf2-frame.c |    2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-Index: gdb-7.4/gdb/dwarf2-frame.c
-===================================================================
---- gdb-7.4.orig/gdb/dwarf2-frame.c	2011-11-17 15:58:35.000000000 +0000
-+++ gdb-7.4/gdb/dwarf2-frame.c	2011-11-17 17:01:03.229359137 +0000
-@@ -1157,7 +1157,7 @@
- 	   DWARF2 register numbers.  */
- 	if (fs->regs.reg[column].how == DWARF2_FRAME_REG_UNSPECIFIED)
- 	  {
--	    if (cache->reg[regnum].how == DWARF2_FRAME_REG_UNSPECIFIED)
-+	    if (0 && cache->reg[regnum].how == DWARF2_FRAME_REG_UNSPECIFIED)
- 	      complaint (&symfile_complaints, _("\
- incomplete CFI data; unspecified registers (e.g., %s) at %s"),
- 			 gdbarch_register_name (gdbarch, regnum),
diff --git a/debian/patches/linux-clear-thread-list.patch b/debian/patches/linux-clear-thread-list.patch
deleted file mode 100644
index 6028d2f..0000000
--- a/debian/patches/linux-clear-thread-list.patch
+++ /dev/null
@@ -1,23 +0,0 @@
-Status: unsubmitted
-
-This patch was for Debian bug #303736.  I now believe it's in the wrong
-place; the generic mourn inferior should do this, perhaps.
-
----
- gdb/linux-thread-db.c |    3 +++
- 1 file changed, 3 insertions(+)
-
-Index: gdb-7.4/gdb/linux-thread-db.c
-===================================================================
---- gdb-7.4.orig/gdb/linux-thread-db.c	2011-11-17 15:58:35.000000000 +0000
-+++ gdb-7.4/gdb/linux-thread-db.c	2011-11-17 17:03:42.573359067 +0000
-@@ -1437,6 +1437,9 @@
-      the inferior, so that we don't try to uninsert them.  */
-   remove_thread_event_breakpoints ();
- 
-+  /* Destroy thread info; it's no longer valid.  */
-+  init_thread_list ();
-+
-   /* Detach thread_db target ops.  */
-   if (!thread_db_list)
-     unpush_target (ops);
diff --git a/debian/patches/series b/debian/patches/series
index c29ba4f..f444d1d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,6 +1,4 @@
-dwarf2-cfi-warning.patch 
 gdb-fortran-main.patch 
-linux-clear-thread-list.patch
 man-page-args.patch
 man-page-order.patch
 linuxthreads_signal_handling.patch

-- 
GNU GDB Debian packaging repository