public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: Fix 'info type-printers' Python error (Clem Dickey, RH BZ 1085576).
Date: Sat, 27 Jun 2026 23:57:04 GMT	[thread overview]
Message-ID: <178260462433.1.8630524352116589231.rpms-gdb-80780792f9d8@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 80780792f9d886c1c3b96894ea25b9b303139ec6
Author : Jan Kratochvil <jan.kratochvil@redhat.com>
Date   : 2015-06-26T15:50:18+02:00
Stats  : +21/-1 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/80780792f9d886c1c3b96894ea25b9b303139ec6?branch=gdb-17.2-rebase-f44

Log:
Fix 'info type-printers' Python error (Clem Dickey, RH BZ 1085576).

---
diff --git a/gdb-type-printers-error.patch b/gdb-type-printers-error.patch
new file mode 100644
index 0000000..aa4c494
--- /dev/null
+++ b/gdb-type-printers-error.patch
@@ -0,0 +1,13 @@
+https://bugzilla.redhat.com/show_bug.cgi?id=1085576
+
+--- gdb-7.8.2/gdb/python/lib/gdb/command/type_printers.py-orig	2015-01-15 11:58:12.000000000 +0100
++++ gdb-7.8.2/gdb/python/lib/gdb/command/type_printers.py	2015-06-26 15:33:43.972460415 +0200
+@@ -47,7 +47,7 @@ class InfoTypePrinter(gdb.Command):
+         sep = ''
+         for objfile in gdb.objfiles():
+             if objfile.type_printers:
+-                print ("%sType printers for %s:" % (sep, objfile.name))
++                print ("%sType printers for %s:" % (sep, objfile.filename))
+                 self.list_type_printers(objfile.type_printers)
+                 sep = '\n'
+         if gdb.current_progspace().type_printers:

diff --git a/gdb.spec b/gdb.spec
index 04b4868..b22af87 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -26,7 +26,7 @@ Version: 7.9.50.%{snapsrc}
 
 # The release always contains a leading reserved number, start it at 1.
 # `upstream' is not a part of `name' to stay fully rpm dependencies compatible for the testing.
-Release: 2%{?dist}
+Release: 3%{?dist}
 
 License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and BSD and Public Domain and GFDL
 Group: Development/Debuggers
@@ -516,6 +516,9 @@ Patch978: gdb-jit-reader-multilib.patch
 # Fix enum e e 'Attempt to use a type name as an expr.' (Keith Seitz, PR 16253).
 Patch991: gdb-cxx-enum-tag.patch
 
+# Fix 'info type-printers' Python error (Clem Dickey, RH BZ 1085576).
+Patch992: gdb-type-printers-error.patch
+
 %if 0%{!?rhel:1} || 0%{?rhel} > 6
 # RL_STATE_FEDORA_GDB would not be found for:
 # Patch642: gdb-readline62-ask-more-rh.patch
@@ -798,6 +801,7 @@ find -name "*.info*"|xargs rm -f
 %patch927 -p1
 %patch978 -p1
 %patch991 -p1
+%patch992 -p1
 
 %patch848 -p1
 %if 0%{!?el6:1}
@@ -1299,6 +1303,9 @@ then
 fi
 
 %changelog
+* Fri Jun 26 2015 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.9.50.20150531-3.fc23
+- Fix 'info type-printers' Python error (Clem Dickey, RH BZ 1085576).
+
 * Tue Jun 16 2015 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.9.50.20150531-2.fc23
 - Fix enum e e 'Attempt to use a type name as an expr.' (Keith Seitz, PR 16253).
 

                 reply	other threads:[~2026-06-27 23:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178260462433.1.8630524352116589231.rpms-gdb-80780792f9d8@fedoraproject.org \
    --to=jan.kratochvil@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /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