public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] fix-dup-patch: Readd ia64 backtrace fixes from 6.1post into 6.3.
Date: Thu, 23 Jul 2026 18:29:04 GMT [thread overview]
Message-ID: <178483134440.1.9513716213159794934.rpms-gdb-e8aabd66a7c0@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gdb
Branch : fix-dup-patch
Commit : e8aabd66a7c09a6c1304c2b56a03d8e5949b9b87
Author : Jeff Johnston <jjohnstn@fedoraproject.org>
Date : 2004-12-14T00:21:54+00:00
Stats : +4/-3 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gdb/c/e8aabd66a7c09a6c1304c2b56a03d8e5949b9b87?branch=fix-dup-patch
Log:
Readd ia64 backtrace fixes from 6.1post into 6.3.
---
diff --git a/gdb.spec b/gdb.spec
index ace61fd..0b0f8fa 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -65,9 +65,6 @@ Patch78: gdb-6.1post-backtrace-nov2004.patch
# Fix to expose multiple constructors to end-user
Patch79: gdb-6.1post-constructor-nov2004.patch
-# Fix panic when stepping an solib call
-# Fix ia64 backtrace
-#Broken: Patch81: gdb-6.1post-ia64-backtrace-nov2004.patch
# Add --readnever hack, and gstack script
#Broken: Patch82: gdb-6.1post-readnever-nov2004.patch
Patch83: gdb-6.1post-gstack-nov2004.patch
@@ -131,6 +128,9 @@ Patch112: gdb-6.3-thread-step-20041207.patch
# Threaded watchpoint support
Patch113: gdb-6.3-threaded-watchpoints-20041213.patch
+# Multiple patches to ia64 backtrace
+Patch114: gdb-6.3-ia64-backtrace-20041213.patch
+
%ifarch ia64
BuildRequires: ncurses-devel glibc-devel gcc make gzip texinfo dejagnu libunwind >= 0.96-3
%else
@@ -177,6 +177,7 @@ and printing their data.
%patch111 -p1
%patch112 -p1
%patch113 -p1
+%patch114 -p1
%patch50 -p1
reply other threads:[~2026-07-23 18:29 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=178483134440.1.9513716213159794934.rpms-gdb-e8aabd66a7c0@fedoraproject.org \
--to=jjohnstn@fedoraproject.org \
--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